EventTransport.h provides the definition for a number of functions whose implementation needs to be provided by the event transport author. See the AP_EventTransport_Functions structure in the API Reference for C++ (Doxygen) for detailed information on these functions.

When the start function is invoked, the event transport is effectively signaled to start accepting incoming messages and pass them onto a codec. Events should not be sent to the correlator until the start function is called.

It is up to the event transport to determine which codec to communicate with from the list of codecs made available to it through the addEventDecoder and removeEventDecoder functions. Typically, a configuration property would be used to specify the codec to be used. If a handle to the desired codec had been stored in a variable called decoder (of type AP_EventDecoder*) when addEventDecoder was called, an event could be passed on to the codec using:

This codec function is described in C/C++ Codec Plug-in Development.

Events should not be sent to the correlator after the stop function has returned. The stop method must wait for any other threads sending events to complete before the stop method returns.