Websocket protocols - tr_json2 vs rssl.json.v2
We are currently using RFA API for bringing in Realtime Market Data from TREP. We are looking to move to strategic Websocket API which is supported by our platform. Looking to understand the protocols supported with Websockets..?
- We are informed that tr_json2 is same as rssl.json.v2. Is that the case..? What is the diff between these two..?
- 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..?
Best Answer
-
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:
1
Answers
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛