BulkDataReceiverDistr1Impl< TCallback > Class Template Reference
#include <bulkDataReceiverDistr1Impl.h>
Inheritance diagram for BulkDataReceiverDistr1Impl< TCallback >:
Collaboration diagram for BulkDataReceiverDistr1Impl< TCallback >:
Public Member Functions | |
| BulkDataReceiverDistr1Impl (const ACE_CString &name, maci::ContainerServices *containerServices) | |
| virtual | ~BulkDataReceiverDistr1Impl () |
| void | cleanUp () |
template<class TCallback>
class BulkDataReceiverDistr1Impl< TCallback >
Constructor & Destructor Documentation
template<class TCallback >
| BulkDataReceiverDistr1Impl< TCallback >::BulkDataReceiverDistr1Impl | ( | const ACE_CString & | name, | |
| maci::ContainerServices * | containerServices | |||
| ) |
Constructor
- Parameters:
-
poa Poa which will activate this and also all other Components. name component name.
template<class TCallback >
| virtual BulkDataReceiverDistr1Impl< TCallback >::~BulkDataReceiverDistr1Impl | ( | ) | [virtual] |
Destructor
Member Function Documentation
template<class TCallback >
| void BulkDataReceiverDistr1Impl< TCallback >::cleanUp | ( | ) | [virtual] |
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.
- Returns:
- void
Reimplemented from BulkDataReceiverImpl< TCallback >.
The documentation for this class was generated from the following file:
