16
●0 ●1 ●3
How can we avoid too many updates with .qos(Timeliness, qosRates) and conflatedInUpdates() methods ?
Hi,
As your query is related to EMA, Alpha was not the right forum.
I moved it to this EMA group.
Kind regards,
AHS
Hi @arnaud.mazzucco,
Thank you for your participation in the forum.
Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question. Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
9.6k
●10 ●7 ●7
Hello @arnaud.mazzucco
EMA does not provide any method to avoid too many updates. It passes all updates as it receives from the server e.g. TREP(ADS/ADH) to the application. Anyway, TREP provides Conflation feature which can specify the time interval at which updates will be sent. For example, set interval 1 second in TREP, TREP merges all updates e.g. 5 updates received from the feed within 1 second then it will publish as one update to EMA. Then, EMA passes the update to the application. Hence, you can avoid too many updates e.g. from 5 updates to 1 update using Conflation feature in TREP. If you are interesting in this feature, please contact Thomson Reuters Account team.
16
●0 ●1 ●3
This methods are applied to ReqMsg objects.
What are the configurations option ?
Like ReqMsg.Timeliness.REALTIME, QosRates.TICK_BY_TICK ?
Thanks a lot
