#include <bulkDataReceiverImpl.h>
Inheritance diagram for BulkDataReceiverImpl< TCallback >:
Public Member Functions | |
BulkDataReceiverImpl (const ACE_CString &name, maci::ContainerServices *containerServices) | |
virtual | ~BulkDataReceiverImpl () |
void | cleanUp () |
virtual AcsBulkdata::BulkDataReceiver< TCallback > * | getReceiver () |
virtual void | openReceiver () |
bulkdata::BulkDataReceiverConfig * | getReceiverConfig () |
virtual void | closeReceiver () |
virtual ACSErr::Completion * | getCbStatus (CORBA::ULong flowNumber) |
virtual void | setTimeout (CORBA::ULong flowNumber, CORBA::ULong timeout) |
virtual void | setRecvName (const char *recvName) |
virtual void | subscribeNotification (ACS::CBvoid_ptr notifCb) |
Private Attributes | |
AcsBulkdata::BulkDataReceiver< TCallback > | receiver |
maci::ContainerServices * | containerServices_p |
|
Constructor
|
|
Destructor |
|
Called after the last functional call to the component has finished. The component should then orderly release resources etc. If this method is overwritten in a subclass, the developer has to make sure that all cleanup performed by the implementation of the base class take place. The best way to do this is to call the implementation of the base itself explicitly, as would be done implicitly in a destructor chain.
Reimplemented from acscomponent::ACSComponentImpl.
Reimplemented in BulkDataReceiver1PerfImpl< TCallback >, BulkDataReceiverDistr1Impl< TCallback >, BulkDataReceiverDistr2Impl, BulkDataReceiverEx2Impl< TCallback >, and BulkDataReceiverEx3Impl< TCallback >.
|
|
|
|
|
|
|
|
|
|
Opens connection creating an out-of-bound channel using TAO A/V services. It creates the Receiver Stream End Point and Flow End Point for the connection with the Sender. The Receiver Stream End Point can be retrieved as an attribute.
|
|
|
|
|
|
|
|
|
|
|