OnixS Eurex ETI Handler C++ library 9.25.0
Users' manual and API documentation
Loading...
Searching...
No Matches
Understanding Handler States

Handler's States

Please find all the available states of the Handler in the list below.

Tracking Handler's State

To track the Handler's state you need to implement OnixS::Eurex::Trading::HandlerStateListener class interface and register an instance with the Handler using OnixS::Eurex::Trading::Handler::registerHandlerStateListener member.

Handler's States Transitions

Let's take a closer look what triggers transitions between the Handler's states.

Handler's States Transition Diagram

Disconnected -> Connecting

Connecting -> Connected

  • When TCP connection to Eurex is established and Logon Request is accepted.

Connecting -> Disconnected

  • When TCP connection to Eurex can't be established.
  • When TCP connection to Eurex is established but Logon request is rejected.

Connected -> Disconnecting

Disconnecting -> Disconnected

  • When TCP connection is closed and the Handler is stopped all the activity.

Connecting the Handler

If the Handler is in the Disconnected state and user code calls OnixS::Eurex::Trading::Handler::connect, user code will receive a callback with new state set to OnixS::Eurex::Trading::HandlerState::Connecting.

If the Handler is in any other state except Disconnected and user code calls OnixS::Eurex::Trading::Handler::connect, the Handler will first disconnects and only after successful disconnect user code will receive a callback with new state set to OnixS::Eurex::Trading::HandlerState::Connecting.

Disconnecting the Handler

If the Handler is in the Disconnected state and user code calls OnixS::Eurex::Trading::Handler::disconnect, user code will not receive any callback.

If the Handler is in any other state except Disconnected and user code calls OnixS::Eurex::Trading::Handler::disconnect, user code will receive a callback with new state set to OnixS::Eurex::Trading::HandlerState::Disconnecting.