When do we use update message processing by EMA?
Currently, we manufacture using EMA.
When connecting to Reuters, data can be acquired via refresh message processing.
However, the sample code describes update message processing and status message processing.
When do we use update message processing?
Also, among the three message processing, Reuters is deciding which process to execute?
I recognize that I do not know what kind of message processing to pass.
Thanks.
Best Answer
-
Hi @hiroyuki.endo,
The Thomson Reuters Market Data System you connect into offers real time market data. That is, when there are changes in the market, such as trades and quotes, you have the option of registering interest in receiving these changes. The changes come through as updates. If you are interested in receiving updates, you register your market data item as a streaming request within the API. When you register interest in receiving streaming updates, you will always receive a refresh message, followed by zero or more update messages. Alternatively, you can decide to not receive updates by registering your market data item as a non-streaming request. In this scenario, you will only receive a refresh, or what is commonly referred to as a snapshot.
The default behavior within the API is to receive streaming updates.
Regarding the three message processing callbacks:
- onRefreshMsg()
This callback will be invoked when you request for a valid streaming or non-streaming market data item.
- onUpdateMsg()
This callback will be called when you request for a valid streaming market data item and that item updates in real time.
- onStatusMsg()
This callback will be called when there are general status events related to your consumer item registration. For example, if you request for an invalid market data item, you will be notified here that your item requested is invalid.
Refer to the series of tutorials offered within the Elektron API for a walkthrough of how the API works.
0
Answers
-
Thank you for your comment.
I understood the movement of these processes.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 中文论坛