Once the Handler is started, it listens to messages from the Eurex ETI message flow, processes it and invokes client code for further processing.
The Handler processes messages asynchronously and uses concept of events and event listeners to notify client code about a particular occasion like reception of record.
For each event like Error Occurred Handler provides an interface (C++ class with pure virtual members) like ErrorListener. Client code must implement this interface (C++ class) to be able to handle events of a particular type. Handler also exposes a member like Handler::registerErrorListener which allows to associate an instance of the event handler with a appropriate event in bounds of a particular instance of the Handler class.
Associating event listener with an instance of the Handler class is also called subscribing to an event.
There're multiple events exposed by the Handler. All events can be logically divided onto high- and low- level event sub-set. High-level events reflect various results of message processing done by the Handler like session events LogonResponse received or Reject received. Low-level events are designed for more control over data processing as well for more flexibility and described in different section of this documentation including Advanced Programming section.
The table below describes Administrative events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from AdminListener):
To register your listener use the Handler::registerAdminListener method of Handler.
The table below describes Strategy Creation events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from StrategyCreationListener):
To register your listener use the Handler::registerStrategyCreationListener method of Handler.
The table below describes Order Handling events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from OrderHandlingListener):
To register your listener use the Handler::registerOrderHandlingListener method of Handler.
The table below describes Quote And Cross Request events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from QuoteAndCrossRequestListener):
| Event/Message | Listener's Method |
|---|---|
| RFQResponse | onRFQResponse |
| CrossRequestResponse | onCrossRequestResponse |
To register your listener use the Handler::registerQuoteAndCrossRequestListener method of Handler.
The table below describes Quote Handling events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from QuoteHandlingListener):
To register your listener use the Handler::registerQuoteHandlingListener method of Handler.
The table below describes Info events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from InfoListener):
To register your listener use the Handler::registerInfoListener method of Handler.
The table below describes TES events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from TESListener):
To register your listener use the Handler::registerTESListener method of Handler.
The table below describes SRQS events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from SRQSListener):
To register your listener use the Handler::registerSRQSListener method of Handler.
The table below describes CLIP events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from CLIPListener):
| Event/Message | Listener's Method |
|---|---|
| CLIPDeletionNotification | onCLIPDeletionNotification |
| CLIPExecutionNotification | onCLIPExecutionNotification |
| CLIPResponse | onCLIPResponse |
To register your listener use the Handler::registerCLIPListener method of Handler.
The table below describes Basket events exposed by the Handler, as well as depicts correspondence between events (messages received) and the methods to be implemented in your listener class (derived from BasketListener):
To register your listener use the Handler::registerBasketListener method of Handler.
