How to maintain an image/cache in EMA? We are moving from RFA MarketData API to EMA.
After going through the EMA documentation, I am not sure if EMA is providing any mechanism to maintain a cached image and applying updates to it.
We used to do it using only a few lines of code in RFA MarketData. We are subscribing to market price service. In RFA MarketData code we maintain a cached full image in a TibMsg object.
TibMsg m_RawImage;
We populate the TibMsg object when we get an initial image from the RFA callback using the following code:
void ProcessItemImage(const MarketDataItemEvent& event)
{
const rfa::common::Buffer& buffer = event.getBuffer();
switch (event.getDataFormat())
{
case MarketDataEnums::Marketfeed:
if (!buffer.isEmpty())
{
TibMsg msg;
TibErr err = msg.UnPack((char*)buffer.c_buf(), buffer.size());
assert(err.code == TIBMSG_OK);
CopyTibMsg(m_RawImage, msg);
.
.
.
When we get a update message callback from RFA we apply the update to the cached full image using the following code:
void ProcessItemUpdate(const MarketDataItemEvent& event)
{
const rfa::common::Buffer& buffer = event.getBuffer();
switch (event.getDataFormat())
{
case MarketDataEnums::Marketfeed:
if (!buffer.isEmpty())
{
TibMsg msg;
TibErr err = msg.UnPack((char*)buffer.c_buf(), buffer.size());
assert(err.code == TIBMSG_OK);
if (err.code != TIBMSG_OK)
return;
UpdateTibMsg(m_RawImage, msg);
.
.
}
bool UpdateTibMsg(TibMsg& image, TibMsg& delta)
{
TibField field;
bool ret = false;
for (field.First(δ); field.status==TIBMSG_OK; field.Next())
{
TibErr err = image.Update(&field);
ret |= (err.code == TIBMSG_OK);
}
return ret;
}
What is the equivalent thing to do in EMA? What object can we cache?
The documentation clearly says this:
Warning! The Data class and all classes that inherit from it are designed as temporary and short-lived objects. For this reason, do not use them as storage or caching devices.
Do we need to implement our own classes for caching and applying updates?
Best Answer
-
Hi @nm
You can follow this tutorial to decode message.
You can extract any interested information from this step.
And you have to create your own class to keep the information from refresh(equivalent to image in TibMsg) or update to your own cache.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 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
- 370 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
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛