Inner Contents | |
Repeating Groups | |
The OnixS::CME::ConflatedTCP::Messaging::SbeMessage represents a Simple Binary Encoding (SBE) message.
The Handler exposes the OnixS::CME::ConflatedTCP::Messaging::MessageHolder class to encapsulate services related to handling SBE messages. It is a template class, which creates an underlying buffer to store an SBE message.
The template parameter SbeMessageType
serves to indicate how the underlying buffer will be interpreted and what type of SBE message it will store.
The OnixS::CME::ConflatedTCP::Messaging::MessageHolder class contains the OnixS::CME::ConflatedTCP::Messaging::SimpleOpenFramingHeader and a strongly typed SBE message over the underlying data buffer.
To access to the strongly typed SBE message, use the OnixS::CME::ConflatedTCP::Messaging::MessageHolder::message method or OnixS::CME::ConflatedTCP::Messaging::MessageHolder::operator->().
The Handler exposes strongly typed SBE message wrappers (e.g.: OnixS::CME::ConflatedTCP::Messaging::NewOrderSingle514
), which provide interfaces to manipulate SBE message fields. These wrappers are used in strongly typed inbound callbacks of the OnixS::CME::ConflatedTCP::SessionListener class (e.g.: OnixS::CME::ConflatedTCP::SessionListener::onExecutionReportNew(const Messaging::ExecutionReportNew522 &, Session *)).
To create an SBE message object, use the OnixS::CME::ConflatedTCP::Messaging::MessageHolder constructor. It creates the underlying buffer and the strongly typed message wrapper around it.
For example:
The following example demonstrates how SBE messages can be created.
null
values, required field values are undefined. This behaviour could be changed using the OnixS::CME::ConflatedTCP::Messaging::FieldsNoInitPolicy template argument.For example: