#include <DataLinkCleanupTask.h>
Inheritance diagram for OpenDDS::DCPS::DataLinkCleanupTask:
Public Member Functions | |
DataLinkCleanupTask () | |
Constructor. | |
virtual | ~DataLinkCleanupTask () |
Virtual Destructor. | |
virtual void | execute (DataLink_rch &dl) |
Handle reconnect requests. |
Definition at line 32 of file DataLinkCleanupTask.h.
OpenDDS::DCPS::DataLinkCleanupTask::DataLinkCleanupTask | ( | ) |
Constructor.
Definition at line 14 of file DataLinkCleanupTask.cpp.
References DBG_ENTRY_LVL.
00015 { 00016 DBG_ENTRY_LVL("DataLinkCleanupTask", "DataLinkCleanupTask",6); 00017 }
OpenDDS::DCPS::DataLinkCleanupTask::~DataLinkCleanupTask | ( | ) | [virtual] |
Virtual Destructor.
Definition at line 19 of file DataLinkCleanupTask.cpp.
References DBG_ENTRY_LVL.
00020 { 00021 DBG_ENTRY_LVL("DataLinkCleanupTask", "~DataLinkCleanupTask",6); 00022 }
void OpenDDS::DCPS::DataLinkCleanupTask::execute | ( | DataLink_rch & | dl | ) | [virtual] |
Handle reconnect requests.
Definition at line 25 of file DataLinkCleanupTask.cpp.
References DBG_ENTRY_LVL.
00026 { 00027 DBG_ENTRY_LVL("DataLinkCleanupTask", "execute",6); 00028 00029 // Assumes that the DataLink is safe for now. 00030 // ciju: I don't believe there are any thread issues here. If any 00031 // the risk seems minimal. 00032 // Not sure about the above statement. Associations could change while 00033 // the Id sequence is being created. That could be trouble. 00034 00035 // Yan: It should be safe to remove now as we made the changes to take a 00036 // snapshot of associations in datalink when reconnect fails and removes 00037 // associations based on the image. It won't remove the new assiciations 00038 // added to the datalink. 00039 dl->clear_associations(); 00040 }