How to pass streamId in a batch message.
Is there a way to pass a specific streamId when encoding a message.
In the example we have this:
for(i = 0; i < itemCount_; i++)
{
itemName.data = marketPriceItemInfoList_[i].itemname;
itemName.length = marketPriceItemInfoList_[i].nameLength;
marketPriceItemInfoList_[i].streamId = ++streamId;
if((ret = rsslEncodeArrayEntry(&encodeIter, &itemName, 0)) < RSSL_RET_SUCCESS)
{
printf("rsslEncodeArrayEntry() failed with return code: %d\n", ret);
return ret;
}
}
which is the for loop when sending a batch request. What I was wondering if there is a way when dealing with encoding a batch request to send a specific streamId in rsslEncodeArrayEntry()?
If not how is the streamId determined when the request is finished being processed?
Best Answer
-
Hi @manning0218,
The streamID in a batch request is set when setting up the request message.
RsslRequestMsg msg = RSSL_INIT_REQUEST_MSG;
...
/* set-up message */
msg.msgBase.msgClass = RSSL_MC_REQUEST;
msg.msgBase.streamId = streamId;However, the streamId associated with the batch request is only used to acknowledge the receipt of the request. When the Provider successfully receives the request, the application will receive a status message indicating the batch was received and will close the stream. It is up to the application, through REFRESH and STATUS messages to determine when the complete batch has been processed.
0
Answers
-
Hi @manning0218
Please refer to the ETA developer guide section on Batch Requests ( section 13.7.1 in v3.0.2 of the document)
As explained the developer specifies a StreamId for the request message and then incremental StreamID are assigned for the items in response.
In the above figure, the consumer uses streamId 4 to send a batch request for three items, having ensured that streamIds 5,
6, and 7 are free and not already being used by existing open streams. The server acknowledges the batch request by responding with an RsslStatusMsg on streamId 4,
and provides the response for each of the three items on streamIds 5, 6, and 7, respectively.As explained by Nick above, streamId 4 will be closed off once you have received the status msg.
1 -
Thank you both for your answers. It makes more sense what is going on with the batch request now.
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 中文论坛