Difference between RefreshMsg and StatusMsg
In our application, we got only RefreshMsg as below at a certain time.
Refresh message (unspecified type), stream open, data suspect, status code None
After that we started to receive StatusMsg as below.
Status message, stream closed, data suspect, status code NotFound
What are the difference between RefreshMsg and StatusMsg ?
When should we expect StatusMsg and when should we expect RefreshMsg to get information about the status of data ?
Can we consider that both of above message are same in regards of he information "data suspect" ?
After receiving above RefreshMsg, should we consider data is completely suspect ? Or can we use existing data for the corresponding instrument?
Thanks in advance.
Best Answer
-
Hello @Ramazan ,
The two are similar:
- Both are possible initial responses when subscribing to a RIC.
- Both are not ok, and depending on your requirements can to be reported to the business tier/user/log/etc.
However, they differ:
- Status = stream closed and instrument not found, is final. It will not change.
- Refresh = stream opened and data suspect is intermittent. As long as the stream remains open, the infra is being recovered and one this happens, will receive further updates, status, whichever is applicable. If SingleOpen is in place, which is default.
Please find the details on Item Refresh Responses and Processing Status Response Messages in RFA Java Developers Guide if you are in Java or in the analogous sections in RFA C++ Developer Guide.
Hope this information helps
2
Answers
-
Hello @Ramazan
While my colleague @zoya faberov answer already has a clear detail of the difference between the Refresh and Status messages, you can find additional details from the 10 important things you need to know before you write a Refinitiv Real-Time application article (please check "Image" and "Status Event" sections).
1
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 中文论坛