For a deeper look into our Elektron API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials |  Articles

question

Upvotes
Accepted
22 3 3 11

ClearCache & DoNotCache values coming in Indications component

We are developing an EMA consumer based application. It is not clear what the consumer application supposed to do when ClearCache or DoNotCache values are received for Indications component of Refresh messages (for Login and MarketPrice domains). Can someone please describe does a consumer application really need to process these values?

elektronrefinitiv-realtimeelektron-sdkconsumer
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@kelvinyoung048

Thank you for your participation in the forum.

Are any of the replies below satisfactory in resolving your query?

If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.

Otherwise please post again offering further insight into your question.

Thanks,

AHS

1 Answer

· Write an Answer
Upvotes
Accepted
11.3k 25 9 14

Consumer application should handle the ClearCache and DoNotCache values only if it is implemented to cache information in response messages.

The ClearCache indicates that existing data in the cache should be cleared before populated with the new data in the received response message. Please see more information in the EMA C++ RDM Usage Guide document.

The DoNotCache indicates that the data in the response message should not be cached.


clearcache.jpg (190.0 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

What is it the right behaviour from the point of view of a Consumer Application that receive refreshMessages and read parameter DoNotCache and ClearCache.

Which action a Consumer Application need to do in those cases?

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.