See: Description
| Interface | Description |
|---|---|
| StateContext |
| Class | Description |
|---|---|
| DisconnectingFromGatewayState |
Responsible for gracefully disconnecting from the MarketFactory Gateways server.
|
| DisconnectingFromVenueState |
Responsible for gracefully logging off of the venue.
|
| EndOfSessionSyncState |
At the end of the synchronization states - even if there was no actual messages replayed - the server will send a test
request to indicate synchronization is complete.
|
| LoggingOnState |
After a successful connection is made in the
OfflineConnectingState this state is responsible for Authentication by sending a Logon message. |
| OfflineConnectingState |
Responsible for opening a connection to MarketFactory.
|
| OfflineWaitingState |
Initial state.
|
| ServerToClientSyncState |
Represents state where the server needs to replay messages to us - the client.
|
| SessionStateContext |
The states behavior and transitions are discussed on The Lab Client Session Management and Venue Connection Management
Initial state is OfflineWaitingState
Each state class contains documentation on their behavior and any cases you should watch out for in your own implementation.