How the real time data we are going to get using RFA Api
Best Answer
-
Hi @harik
Please work through the whole tutorials at least as far as step 7 to get a fuller understanding of how the API works.
You will note the MyClient class of the example which is derived from rfa::common::Client and has to implement the processEvent callback method.
The example code specifies the above class instance as the event handler when it calls registerClient for the Login Request and the MarketData item request.
Therefore as and when the API receives events from the server, the API will call the processEvent handled with the event payload and the processEvent will process the event.
The dispatching of these events is controlled by the example's RdmApp:run() method which is running and dispatching events in the main application thread.
The processEvent is called by the API in the API thread context - asynchronously as it receives events from the server.
0
Answers
-
Hi @harik
RFA event model uses event handlers/callbacks to process events received from the server
See RFA C++ Tutorials for more details. If you are using RFA Java or RFA .Net you can access similar tutorials by clicking the Available Editions: Java, .NET links.
IF you are writing a new application and using C++ or Java then I strongly recommend you use the Elektron Message API of the ElektronSDK -which is our strategic offering and much easier to learn and implement. RFA is now feature-complete / in maintenance mode.
0 -
Please advise which language you are using and which examples you are referring to?
0 -
RFA C++ and step 4 in download examples .I also checked examples in setup .There are also straight forward call instead of call back
0 -
Apart from a suggestion from Umer. I would suggest you find the details about the Event Distribution Model from RFA Developer Guide(RFA_DevelopersGuide.pdf) which provided in RFA C++ packages(under folder <RFA Install Folder>/Docs).
Section 6.4.1 Event Distribution Model and 10.1.1.3 Process Event in Client has the information about the processEvent callback.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 705 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.2K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 569 WebSocket API
- 40 FX Venues
- 16 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 24 RDMS
- 2.2K Refinitiv Data Platform
- 879 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 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
- 123 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 919 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 103 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛