SBE Message

Inner Contents
	Message Fields
	Repeating Groups

Detailed Description

The OnixS::CME::ConflatedTCP::Messaging::SbeMessage represents a Simple Binary Encoding (SBE) message.

MessageHolder class

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->().

Strongly Typed SBE Message Wrappers

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 *)).

Note

Strongly typed SBE message wrapper classes do not have an underlying buffer and work only over an external buffer. Therefore, one needs to make sure that the lifetime of a strongly typed SBE message class object is the same as the lifetime of the buffer. For example, one should not use the delivered strongly typed SBE message object outside the inbound callback, since it uses an internal receiving buffer.

Constructing SBE Message

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.

using namespace OnixS::CME::ConflatedTCP;
using namespace OnixS::CME::ConflatedTCP::Messaging;

// Constructs a "New Order - Single" message,
// optional field values are set to their `null` values,
// required field values are undefined.
typedef MessageHolder<MarketDataRequest205> MarketDataRequest;

MarketDataRequest request;

std::cout << "Request " << request.message() << std::endl;

Note

By default, the OnixS::CME::ConflatedTCP::Messaging::MessageHolder constructor sets optional fields to their null values, required field values are undefined. This behaviour could be changed using the OnixS::CME::ConflatedTCP::Messaging::FieldsNoInitPolicy template argument.

For example:

using namespace OnixS::CME::ConflatedTCP;
using namespace OnixS::CME::ConflatedTCP::Messaging;

// Constructs a "New Order - Single" message, both requird and optional field values are undefined.
typedef MessageHolder<MarketDataRequest205, GetMaxMessageSize<MarketDataRequest205, DefaultMaxGroupItems>::Size,
    FieldsNoInitPolicy> MarketDataRequest;

MarketDataRequest request;

std::cout << "Request " << request.message() << std::endl;