order of source directory updates and handling them correctly
tr.txtI am making the following request using rmdsTestClient against sink_driven_source + ADS combination as provider:
./rmdstestclient -S hEDD -ct rssl -p 14001 -itemList IBM,AAPL.O,MSFT.O -X -l stdout
I received response for the symbols with groupID 1 and 2. Then I killed sink_driven_source to simulate service down or ServiceState = 0. I noticed that I received two RSSL_DMT_SOURCE updates for the two groupIds as dataState="RSSL_DATA_SUSPECT" followed by another RSSL_DMT_SOURCE update as ServiceState = 0. I have attached the XML response too.
My question is for source directory update, is it correct to assume that source directory updates are received in the order of GROUP level updates followed by SERVICE level update? Does that also mean that an Consumer application should clear all prior source directory information and react to source directory update as it comes?
Best Answer
-
I think that this behaviour is specific to ADS and it demonstrates the recommended practice to handle group and service level update. However, you shouldn't expect that other servers or third-party providers will follow this behaviour.
When the service is down, one service level update is enough to change the ServiceState and the Status of all items provided by this service. The following is the description of the Status element in the Source Directory State Filter Entry.
To handle, the source directory update, the application should follow the action of the map entry and filter entry in the update message.
For more information, please refer to the following sections in the RDM Usage Guide.
0
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛