Eikon .NET API DispatcherFrame
I am building an application that will use eikon .net api along with redi api.
I need to process pricing in the background thread and call subscription as needed. I googled 'DispatcheFrame' but still not clear how I should be structuring my code.
1. Current example creates/starts subscription and then calls Dispatcher.PushFrame() which stops code from executing next line. How do I add new subscriptions?
2. Any problem if I were to wrap this in a worker thread? It seems to work but not sure whether it will cause problem.
I'd appreciate advice on how I should be structuring the code in multi threaded environment. Currently, I am testing it in the console app but eventually it will be a gui app.
Best Answer
-
In addition to the response from @Zhenya Kovalyov, I would very strongly recommend implementing all data retrieval on a single thread. It can very well be a worker thread, but it should be a single thread and Windows message pump must be running on this thread. In a GUI application it's best to do all data retrieval on the GUI thread.
0
Answers
-
@39783854-26aa-4fea-bc93-00b2ec21f8bb the .NET api requires manual pumping of the event loop, DispatcherFrame is just a replacement for Application.DoEvents(). In the console app context (sample apps) it is required, so program is prevented from exiting before the event arrives.
I do not think using it in a multi-threaded environment is going to cause problems.
0 -
I can have a separate thread create and process all the message. However, if I want to change subscriptions should I have reference to subscription object from other thread and directly update? (subscription.AddRic/etc)
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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛