What does RespMsg::ClearCacheFlag actually do?

ed.mcconnell

I am publishing several records which comprise a chain over RSSL/OMM. So 0#MYCHAIN, 1#MyChain, etc.

Currently existing chains use short link FIDs (e.g. LINK_#) and I've changed our publishing to use long link FIDs (LONGLINK#). As a result, I want to clear out any any short-link FIDs which exist in the record when I publish the long-links. Easy , right? No, nothing is easy with RFA.

I use a PostMsg with an embedded Refresh message setting rfa::message::RespMsg::ClearCacheFlag in the indication mask. It does overwrite the existing fields but any subsequent updates to that record cause Eikon to only show the updated fields (i.e. it looks like the other FIDs have disappeared).

What should I be sending to RFA to work correctly in this use-case?

BTW, the fields *DO* appear to be in the cache, it's just that EIKON only seems to show the updated fields.

paulofogaca

Hi

I think you need to set ClearCacheFlag only for refresh message, make subsequent updates without that flag. So you need am internal boolean variable in your code such as 'imageSent', if set to false you post a refresh with ClearCacheFlag and set imageSent=true, later when posting gain you see the imageSent is true and post an update without ClearCacheFlag set. You need a 'imageSent' flag for each (Service, Ric) pair.

Paulo.

ed.mcconnell

Hi Paulo,

That's what I'm doing. I send an initial (Post+embeddedRefresh+ClearCache) followed by (Post) messages.

Are you from Reuters?

many thanks,

Ed.

paulofogaca

Hi Ed,

Are the following posts also Refreshes? I think they should be updates without ClearCache.

You need to control each post with its own 'imageSent' flag.

What is the service you are posting to? I have already made similar thing in the past when posting to an ADH cache. I think this will not work with other services such as ATS or DCS.

Yes, I am from Reuters.

Tks

Paulo