to directly connect to RCC to contribute data which approach is better 1.) Real time SDK or 2.) webs
Best Answer
-
Hello @manpreet.singh
The WebSocket API is designed for easy to develop and support various programming languages via the standard WebSocket connection and JSON message format. However, the application needs to manually control the connection and session logic by itself.
The Real-Time SDK uses Refinitiv's proprietary TCP-based connection called RSSL. The RSSL connection encodes data in binary format which is highly optimized for data distribution more than a JSON string format in a WebSocket connection. The EMA API (part of the SDK) is also handling the connection for the application. However, the SDK currently supports the Java and C++ programming languages.
1
Answers
-
Thanks a lot for detailed answer, Can you also describe which is a better solution(websocket vs real time SDK) in terms of performance for us. Our use case is to send the pricing data every 10 seconds?
0 -
Hello @manpreet.singh
The Real-Time SDK (RTSDK) always has a better performance than the WebSocket API because the data is encoded in a binary format.
However, it is also based on your use case (numbers of posting items, the language and library/framework that you are using, etc) that the WebSocket API performance may be enough for your scenario.
1 -
Thanks a lot again, see in our scenario we are targeting to send pricing data after every 5-10 sec interval using Python, will websocket is good for this use case(sending data after every 5-10 sec) can you confirm? @wasin.waeosri
0 -
Hello @manpreet.singh
How many items do you want to send pricing data to RCC? Are you planning to use the RCC direct connection or via RTDS (aka TREP)?
1 -
1) There are 6-8 attributes we are going to send such as ticker, price , volume, window interval / others. We want to send the pricing data of 6-8 attributes every 5-10 seconds interval
2) We want to use direct connection only for websockets0 -
Hello @manpreet.singh
Could you please clarify my understanding?
- You are planning to contribute 6-8 items' pricing data to RCC
- Each item contains 5-10 fields of data
- You are planning to send data every 5-10 seconds interval
- You will connect to RCC directly
If so, the WebSocket API is enough for your requirements. You can find more detail about how to use WebSocket API direct connect to RCC from this Contributing Data to Refinitiv Contributions Channel (RCC) via WebSocket tutorial page.
1 -
1.)We are planning to contribute 50,000(IBM/GOOGLE/OTHERS) security pricing data to RCC
2.)Each item contains 5-10 fields of data
3.) we are planning to send data every 5-10 seconds interval
4.)we will connect to RCC directly
Please advice python websocket (directly to RCC) is sufficient or not in term of performance.
0 -
@wasin.waeosri Hi, can you please provide solution for the above query?
0 -
Hello @manpreet.singh
Please see the answer and discussion on this https://community.developers.refinitiv.com/questions/80465/confirmation-of-python-websocket-directly-to-rcc-i.html post.
0
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 中文论坛