OnixS C++ CME MDP Conflated TCP Handler  1.1.0
API Documentation
Session Storage

Inner Contents

 Memory-based Session Storage
 
 File-Based Session Storage
 
 Asynchronous File-Based Session Storage
 
 Pluggable Session Storage
 

Detailed Description

By default, the Handler uses File-Based Session Storage, so it stores incoming and outgoing messages and session's state data in files in the OnixS::CME::ConflatedTCP::SessionSettings::storageDirectory folder.

However, it is possible to keep all session-related data in memory using the Memory-based Session Storage.

Also, one can use asynchronous-file-based-session-storage, which combines excellent performance with the File-Based Session Storage functionality.

Yet another option is to use the Pluggable Session Storage.

Restoring Session State

When the OnixS::CME::ConflatedTCP::Session object is created, the session state (OnixS::CME::ConflatedTCP::Session::uuid, OnixS::CME::ConflatedTCP::Session::inSeqNum, OnixS::CME::ConflatedTCP::Session::outSeqNum, OnixS::CME::ConflatedTCP::Session::previousSeqNo, OnixS::CME::ConflatedTCP::Session::previousUuid, etc.) is restored from the session storage.

To start a session as a new one (so-called "clean start"), either remove the session storage files from the previous runs or call the OnixS::CME::ConflatedTCP::Session::reset(bool startOfWeek = false) method.

When the session is finished, the session storage files are not needed anymore. They can be backed up, and later a new Conflated TCP session with a new UUID will start message sequence numbers from 1.

The usual practice is to back up log files at the end of the business week (so-called "End Of Week procedure") to generate a new UUID and start the sequence numbers from 1 at the beginning of the next week.