Requesting vendor-delayed RICs
Why does ADS prevent consumers from requesting vendor-delayed RICs when Delay is enabled?
Best Answer
-
The reason you're not allowed to request vendor delayed RICs when delay capability is enabled is because the vendor delayed stream (/RIC) is used to populate image in the cache and the initial response and updates to applications while the real-time stream (RIC) is being aged in the delay files for 20-30 minutes depending on delay rules.
So what happens in ADH/ADS when getting a request for example TRI.N is creating consumer item for TRI.N and creating producer items for TRI.N and /TRI.N and make actual requests to the upstream components. The consumer item for TRI.N will then multiplex responses from both producer items seamlessly for applications to get the best data available at a time.
The key reason for not allowing /RICs to delay services from applications is to avoid complexity of many-to-many relationships of consumers and producer items here as doing so will introduce a lot of changes and overly complex logic in the current design just to achieve this (not that it’s not possible to make changes but the size of changes and impact to achieve this).
This logic is the same since the old day with RDTIC. The decision was made back then based on the assumption that Delay capability is enabled so the better quality of delayed data is already available through the request for TRI.N item so it’s not worth introducing more complexity to support request for /TRI.N. You can simply request for TRI.N and ADH/ADS will manage to stream the best delayed data available whether it’s from /TRI.N or delayed stream of TRI.N. If this is not what you want, you can disable Vendor Delayed feature from ADH/ADS so you can request for /RICs but you will not be able to get the /RICs image populated into the responses for the request for RICs that is still being aged in the files.
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 中文论坛