The Handler supports all three types of Initialization and Binding operations.

Beginning of Week Initialization and Binding

"Beginning of Week initialization and Binding" takes place during the very first connection establishment for the week.

To reset the inbound and outbound sequence numbers to 1 as well as to generate a unique UUID, use the following sequence of calls:

if (session.negotiated())
    session.reset(true);
session.connect(CounterpartyHost, CounterpartyPort);

Mid-Week Initialization and Binding

"Mid Week initialization and Binding" takes place when a new session with a new globally unique UUID is created during the week.

To reset the inbound and outbound sequence numbers to 1 as well as to generate a unique UUID, use the following sequence of calls:

if (session.negotiated())
    session.reset(false);
session.connect(CounterpartyHost, CounterpartyPort);

Intra-Session Binding (Binding without Initialization)

"Intra-Session Binding" takes place when the session is connected again after a successful Beginning of Week Initialization and Binding or Mid-Week Initialization and Binding. In this case, the same UUID is used, and the sequence number series is continued from the previous connection.

For example:

// "Beginning of Week Initialization and Binding" or "Mid-Week Initialization and Binding".
// ...
session.disconnect();
assert(session.negotiated());
session.connect(CounterpartyHost, CounterpartyPort);

See also: Automated Downloading of GTC and GTD Orders; Universally Unique Identifier (UUID)