question

Upvotes
Accepted
Paolo Parlapiano avatar image
35 ●3 ●2 ●9

OMM and Record Templates

HI,
on the legacy MarketFeed\SSL protocols we had the concept of Record Templates, which was also natively supported on SFC C++ via the RTRRTRecordImpl::setRecordTemplateNumber( RTRString * ) method and other similar methods. Using RFA C++ instead, the template number was set directly in the REC_TYPE field.

Anyway, the SFC C++ documentation had a note saying that "Record templates are a legacy concept on Triarch. Very few components actually use them".

My question is then the following: migrating a provider application from SFC C++ \ RFA C++, supporting SSL\MarketFeed, to an EMA C++ based application supporting OMM \ RSSL, should the application continue to support record templates? Or is this concept no longer necessary on the new protocols?

Thanks

Best Regards,

Paolo

elektronrefinitiv-realtimeelektron-sdkrrtrfaema-apielektron-message-apisfc
icon clock
10 |1500

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

1 Answer

Upvote
Accepted
Gurpreet avatar image
13k ●32 ●12 ●18

Hello @Paolo Parlapiano,

The answer will depend on which application(s) are using the provided data, and if it is decoding and using/storing the record template number. It is highly unlikely that a recent consumer application will use it, but you might have legacy applications using that field.

So, even though it is no longer needed for OMM/RSSL protocol, it won't hurt to carry one additional field to maintain backwards compatibility.

icon clock
10 |1500

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

Click below to post an Idea Post Idea