Define the interface for the dispatching strategies. More...
#include <CEC_Dispatching.h>
Public Member Functions | |
| virtual | ~TAO_CEC_Dispatching () |
| destructor... | |
| virtual void | activate ()=0 |
| virtual void | shutdown ()=0 |
| virtual void | push (TAO_CEC_ProxyPushSupplier *proxy, const CORBA::Any &event)=0 |
| The consumer represented by proxy should receive event. | |
| virtual void | push_nocopy (TAO_CEC_ProxyPushSupplier *proxy, CORBA::Any &event)=0 |
Detailed Description
Define the interface for the dispatching strategies.
The EC may be configured with different dispatching strategies, for instance, it can use a pool of threads to dispatch the events, or a set of queues with threads at different priorities for each queue or can simply push the event to the consumer in FIFO order.
Constructor & Destructor Documentation
◆ ~TAO_CEC_Dispatching()
|
virtual |
destructor...
Member Function Documentation
◆ activate()
|
pure virtual |
Initialize all the data structures, activate any internal threads, etc.
Implemented in TAO_CEC_Reactive_Dispatching, and TAO_CEC_MT_Dispatching.
◆ push()
|
pure virtual |
The consumer represented by proxy should receive event.
Implemented in TAO_CEC_Reactive_Dispatching, and TAO_CEC_MT_Dispatching.
◆ push_nocopy()
|
pure virtual |
Implemented in TAO_CEC_Reactive_Dispatching, and TAO_CEC_MT_Dispatching.
◆ shutdown()
|
pure virtual |
Deactivate any internal threads and cleanup internal data structures, it should only return once the threads have finished their jobs.
Implemented in TAO_CEC_Reactive_Dispatching, and TAO_CEC_MT_Dispatching.
The documentation for this class was generated from the following files:
