question

Upvotes
Accepted
bneway avatar image
57 ●3 ●2 ●6

Validation of RSSL Consumer application using a packet capture.

Hi.

I am looking for more ways to test and validate my RSSL Consumer application. With many market data feeds, I am able to run a replay of the data to verify the application/parser works as well. Theoretically, were I to get permission to get a PCAP of a current RSSL consumer application we have interacting with a real UPA server, am I right to assume there would be little to nothing I could do with it to increase validation coverage? Unlike some other market data feeds, I am not able to just "feed in" the raw bytes captured, since obviously UPA is a proprietary API and so I would only be able to interact with the data through the API. Am I wrong about this? Is there anything that others have done to validate their consumer by getting a packet capture and using certain techniques?

Thank you very much.


#technologylinuxctestingupa-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
Jirapongse avatar image
83.1k ●281 ●53 ●77

@bneway

Thank you for reaching out to us.

RSSL is a proprietary protocol so the Real-Time SDKs are required to decode the RSSL protocol.

Moreover, we don't provide the public documents or tools that show how to decode the RSSL protocol so clients can't decode it from PCAP files.

Typically, we use XML trace files to validate the retrieved messages.

We have sample tools to process the XML trace files.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.