'Classic' CCA c++ binding (ccaffeine-only)  0.5.7
Public Member Functions
classic::gov::cca::ConnectionEventService Class Reference

UNADOPTED standard ConnectionEvent Service Interface. More...

#include <ConnectionEventService.h>

Inheritance diagram for classic::gov::cca::ConnectionEventService:
Inheritance graph
[legend]
Collaboration diagram for classic::gov::cca::ConnectionEventService:
Collaboration graph
[legend]

List of all members.

Public Member Functions

virtual ~ConnectionEventService ()
 obligatory vdtor
virtual void addConnectEventListener (ConnectionEventListener *l) CLASSIC_CCA_PURE
 Register l as interested in post-notification of connections.
virtual void addDisconnectEventListener (ConnectionEventListener *l) CLASSIC_CCA_PURE
 Register l as interested in pre-notification of disconnections.
virtual void removeConnectEventListener (ConnectionEventListener *l) CLASSIC_CCA_PURE
 Remove l as interested in post-notification of connections.
virtual void removeDisconnectEventListener (ConnectionEventListener *l) CLASSIC_CCA_PURE
 Remove l as interested in pre-notification of disconnections.

Detailed Description

UNADOPTED standard ConnectionEvent Service Interface.

Should be able to get and use one of these from the Services implementation during a setServices call.

The CCAT Event Bus model could conceivably be used to implement this, but this interface and its subsidiaries place much smaller burden on the framework writer. Further, with an asynchronous bus delivery mechanism it may be harder to guarantee the event order condition on the DisconnectingConnectionEvent.

From the CCAT event page: A publisher can send events directly to listeners without an intervening event channel. The ports can simply be connected together. This is an instance of a 1-to-n uses-to-provides connection, which is permitted by the CCA specification. Connecting multiple providers is also possible. The CCA specification allows general m-to-n connections between m uses ports and n provides ports.

We note that while possibly allowing it, the specification does not require or (presently, 8/2000) provide a standard way to allow MxN Port connections.


Constructor & Destructor Documentation

obligatory vdtor

{}

Member Function Documentation

Register l as interested in post-notification of connections.

Register l as interested in pre-notification of disconnections.

See also:
www.extreme.indiana.edu/ccat/event_service.html

Remove l as interested in post-notification of connections.

Remove l as interested in pre-notification of disconnections.


The documentation for this class was generated from the following file: