Websocket protocols - tr_json2 vs rssl.json.v2

Hello @Yatin

Question 1: We are informed that tr_json2 is same as rssl.json.v2. Is that the case..? What is the diff between these two..?

Answer: The tr_json2 and rssl.json.v2 are the same WebSocket connection that uses the JSON message format.

Question 2: What is the diff between RSSL RWF vs JSON format..? Are both of these supported with Websockets to connect to TREP to fetch Realtime Market Data..?

Answer:

• RSSL RWF is Refinitiv (LSEG) proprietary TCP-based connection that uses binary to represent data. This connection type is optimized and designed for high-performance data distribution. This connection type is supported by the Real-Time SDK (RTSDK - C#, C/C++, and Java) only.
• JSON format is "a string" message format. It is aimed for easy-to-read, easy-to-parse by other services, and supports various Programming languages.
• The RSSL RWF uses binary to represent data, so the message size is smaller than JSON string format and gives a better performance than JSON string.
• RSSL RWF supports the RSSL connection only.
• Both RSSL and WebSocket can consumer real-time data from Refinitiv Real-Time platform

If the performance is main concern, I highly recommend the client upgrade to the Enterprise Message API (EMA API) using the RSSL connection.

The EMA API gives higher performance than the WebSocket API and EMA API is a higher-level API than the WebSocket API.

• EMA API manages the connection and subscriptions for the application.
• WebSocket API is a lower-level protocol that the application needs to handle everything by itself.

The client can check the following articles for more details:

• Choosing a Refinitiv Real-time Streaming API
• Migrating from the Legacy Robust Foundation API (RFA) to the Enterprise Message API (EMA)