• Programming Guide
  • Api Documentation
  • OnixS CME iLink3 Handler for .NET Core, version 1.4.2
Show / Hide Table of Contents
  • Introduction
  • System Requirements
  • Getting Started
    • Error Reporting
    • Licensing
    • SBE Message
      • Tag-based Messaging
      • Message Fields
      • Repeating Groups
    • iLink 3 Session
      • Universally Unique Identifier
      • Establishing iLink3 Connection
      • Exchanging Messages
      • Message Sequence Numbers
  • Configuring the Handler
    • Configuration File Examples (XML or JSON)
  • Logging
  • Session Storage
    • File-Based Session Storage
    • Memory-based Session Storage
    • Asynchronous File-Based Session Storage
    • Pluggable Session Storage
  • Advanced Programming
    • Thread Safety
    • Session Initialization and Binding
    • Session States
    • Listening to Session Events
    • Handling NotApplied Messages
    • Handling Business Reject Messages
    • Automated Downloading of GTC and GTD Orders
    • Reconnection
    • Fault Tolerance
    • Understanding Send Latency
    • Strongly Typed Messages
  • Best Practices
    • Low Latency Best Practices
  • Glossary
  • Support

Session Initialization and Binding

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 Universally Unique Identifier (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();

if (!session.Negotiated)
    throw new Exception("Session is not negotiated");

session.Connect(CounterpartyHost, CounterpartyPort);

See Also

Automated Downloading of GTC and GTD Orders Universally Unique Identifier (UUID)

In This Article
Back to top Copyright © Onix Solutions.
Generated by DocFX