Understanding Handler States

Handler's States

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

State	Description
OnixS::Eurex::Trading::HandlerState::Disconnected	The Handler is disconnected.
OnixS::Eurex::Trading::HandlerState::Disconnecting	The intermediate state when the Handler is not disconnected but not connected.
OnixS::Eurex::Trading::HandlerState::Connected	Handler is connected.
OnixS::Eurex::Trading::HandlerState::Connecting	The intermediate state when the Handler is not connected but not disconnected.

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.

Disconnected -> Connecting

• When OnixS::Eurex::Trading::Handler::connect is called.
• When the Handler is restarting.

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

• When OnixS::Eurex::Trading::Handler::disconnect is called.
• When TCP connection is disconnected and no reconnect attempts left.

Disconnecting -> Disconnected

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