stream id after registerClient call

Best Answer
-
Hello @vishal.anand ,
I suspect that you may be looking for a handle that is returned by registerConsumer call, that can be used to unregister the item, for example:
long handle = consumer.registerClient(reqMsg.serviceName("ELEKTRON_DD").name("IBM.N"), appClient);
Thread.sleep(5000);
consumer.unregister(handle);If you are looking for the streamId it can be found in the received messages, in the attributes, for example:
UpdateMsg
streamId="5"
domain="MarketPrice Domain"
updateTypeNum="1"
name="IBM.N"
serviceId="356"
serviceName="ELEKTRON_DD"
Payload dataType="FieldList"
FieldList
FieldEntry fid="22" name="BID" dataType="Real" value="130.510000"
FieldEntry fid="25" name="ASK" dataType="Real" value="130.540000"0
Answers
-
Yes my bad, I am using EMA Real-Time-SDK-2.0.6.L1.linux
0 -
@zoya faberov Is there any way I can relate the log handle returned by registerClient call to that of streamId? How would i know the log handle returned and the streamId are for the same request? Do we expect both to be the same?Hi0
-
Hello @vishal.anand ,
You can:
From a refresh or an update, we can obtain both handle and streamID.
To obtain handle:
event.handle();
To obtain streamId we parse Attrib part of the message, see example 290 Custom_Decode for the code.
From that point on, you can create a map and store the relationship, and always map the handle and the streamId.
I am curious, what is your use case, why is it helpful to relate the two?
0 -
@zoya faberov . That works and actually I used event.getHandle().Thanks
The use case is that we are writing a client to Feed Handler that will send request and check how many were received back and how many had errors. Basically some kind of monitoring app so the app needs to know specifically which requests were solicited.
0 -
@vishal.anand ,Hello
If all your requests are for same MarketPrice domain, you can simply keep the map of the requested item names, and track the received Refreshes and Statuses against them. Each requested item should result either in a Refresh or in a Status.
Number of requested items = first refreshes + first statuses
Handles will allow you to unsubscribe when the subscription is no longer needed.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 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
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- 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
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛