How is the completion event different than status message indicating event stream is closed
Hello, we use RFA 8.2 C++ api to consume Level1 and Level2 market data with Open DACS integrated. We want to ensure that DACS check fail for symbols for which api will never give any data in the future. It could be because symbol is bad .. etc. We plan to handle this using status message indicating event stream is closed for given subscription.
Alternative approach is to register for completion event and do it in completion event. But problem with this approach is that, completion event is received even for subscription closed by user by calling `unregisterClient()`.
What approach do you suggest?
Best Answer
-
Thank you for reaching out to us.
As mentioned in the developer guide, the application should use the isEventStreamClosed() function.
0
Answers
-
@Jirapongse We already check for event stream state value if it is "Closed" OR "ClosedRecover" OR "Redirected" in status message callback. Do we still need to check for `isEventStreamClosed()`?
Also Is there a use case where we expect status message to be received indicating even stream is closed but completion event is NOT expected. This is obviously after assumption application registered for completion event.Is there any difference?
0 -
The isEventStreamClosed() should cover ComplEvent, Closed, ClosedRecover, Redirected, and NonStreaming.
However, please contact the API support team directly via Contact Premium Support to confirm it.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 251 ETA
- 555 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 916 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛