Successive batch requests behavior

[ja-pollard]

I'm opening this on behalf of a client working with EMA Java 3.7.2.0. Could someone please verify if they are receiving the expected behavior?

Reference: https://community.developers.refinitiv.com/questions/111826/handle-concurrent-snapshot-requests-with-overlappi.html

[ja-pollard]

I've put together an example based on ex370_MP_Batch which I've attached as a text file. The output which is also attached shows two requests/responses for <BMO.TO> and <RY.TO> which is exactly what the client is reporting and questioning.

Consumer.java.txt

consumer.log.gz

[L-Karchevska]

@ja-pollard Thank you for raising this issue! Regarding the part of the question related to new requests being sent out for the same items, this is by design of the API. In case the application makes a snapshot request for the item, as soon as the refresh is received, the API is done with it and the stream associated with the item is closed. Hence, when another request is made by the application for the same item, the API sends out a new request, according to the nature of the real time data. This is opposed to the streaming request where the API keeps the stream associated with the item open and receives all refreshes and updates associated with the item, hence at a given moment of time it has the most up-to-date information about the item and there is no need to re-send a request by the API if the application submits the same request.