[Ema]C++ How to decide the opportunity to request chain and quote info
Hello:
I develop in EMA C++ with Elektron-SDK1.2.1.linux to request HKSE quote info.
I want to know the opportunity for requesting chain and quote, such as:
1、Which slot is the best time to request chain?
as I know, the HKSE begin to send msg at 6:00 am, can I request the chain from Eletron before 6:00 am?
2、Should I unRegisterClient when the HKSE is closed?
HKSE will be closed at 16:30, is it necessary to unRegisterClient at 16:30.
3、Does the updateMsg will be send if the chain update?
if che chain of HKSE update in the afternoon, although it is rare, How can I get the new chain?
Best Answer
-
Hi @luxiangyuan
If you create a streaming request (which is the default) then you will continue to receive Update Msgs as and when the Chain changes at any time of the day - until you call unregisterClient.
So, it is your decision if you start a new request at the start of the day and then close the stream after the market closes OR you continue to receive the updates 24hrs a day.
As to whether you will receive any Chain updates when the market closes, that is something you need to check with HKSE or the Content helpdesk.
With regards afternoon update of chain, if you keep the stream open and do NOT close the stream (by calling unregisterClient) you will receive any such update to the chain as and when it occurs.
0
Answers
-
hello Umer Nalla
I am so sorry that I have been busy with too many other things.
Do you know how other customers realize?
or could you gave some suggestion?
thanks!
0 -
Hi @luxiangyuan
Firstly you need to check with Content helpdesk just how often the chain updates. This may help you decide - so if they confirm the chain will not update after Market Close then you could unregister after market close and start afresh every morning.
For client developers who do use Chains, the usage varies - some like to shut down after market close and startup their application every morning. Others, build the chain at application startup and and then leave the application running long term - updating the chain when there as updates.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 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
- 370 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛