• 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 Storage

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 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 Session object is created, the session state (Uuid, Negotiated, InSeqNum, OutSeqNum, PreviousSeqNo, 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 Reset(Boolean) method.

When the session is finished, the session storage files are not needed anymore. They can be backed up, and later a new iLink 3 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.

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