Collaboration diagram for TAO_EC_Event_Channel_Attributes:
Public Member Functions
|TAO_EC_Event_Channel_Attributes (PortableServer::POA_ptr supplier_poa, PortableServer::POA_ptr consumer_poa)|
|Can consumers or suppliers invoke connect_push_* multiple times? |
|The POAs. |
|Only the EC can read the private fields. |
The event channel implementation is controlled by two mechanisms: The EC_Factory that provides the strategies for the EC implementation. The EC attributes that define constants and values required by the EC construction. This class encapsulates those constants and values, providing an easy mechanism to extend the attributes without requiring changes in the EC constructor.
|TAO_BEGIN_VERSIONED_NAMESPACE_DECL ACE_INLINE TAO_EC_Event_Channel_Attributes::TAO_EC_Event_Channel_Attributes||(||PortableServer::POA_ptr||supplier_poa,|
The basic constructor. The attributes listed as arguments are *required* by the EC, and no appropiate defaults are available for them.
|friend class TAO_EC_Event_Channel_Base
Only the EC can read the private fields.
Can consumers or suppliers invoke connect_push_* multiple times?
It not zero the event channel will send disconnect callbacks when a disconnect method is called on a Proxy. In other words, if a consumer calls disconnect_push_supplier() on its proxy the EC will invoke disconnect_push_consumer() on the consumer. A similar thing is done for suppliers. It is a matter of debate what the spec requires for the regular event service.
The scheduling service that we will use with this event channel. Notice that this is optional and will only take effect if the EC is configured with the right filtering strategies.