RTI Connext Modern C++ API
Version 5.2.0
|
The definition of the dds::core::safe_enum LivelinessKind. More...
#include <PolicyKind.hpp>
Public Types | |
enum | type { AUTOMATIC, MANUAL_BY_PARTICIPANT, MANUAL_BY_TOPIC } |
The underlying enum type. More... | |
The definition of the dds::core::safe_enum LivelinessKind.
The underlying enum
type.
AUTOMATIC |
[default] The infrastructure will automatically signal liveliness for the dds::pub::DataWriter (s) at least as often as required by the A dds::pub::DataWriter with this setting does not need to take any specific action in order to be considered 'alive.' The dds::pub::DataWriter is only 'not alive' when the participant to which it belongs terminates (gracefully or not), or when there is a network problem that prevents the current participant from contacting that remote participant. |
MANUAL_BY_PARTICIPANT |
RTI Connext will assume that as long as at least one dds::pub::DataWriter belonging to the dds::domain::DomainParticipant (or the dds::domain::DomainParticipant itself) has asserted its liveliness, then the other Entities belonging to that same dds::domain::DomainParticipant are also alive. The user application takes responsibility to signal liveliness to RTI Connext either by calling dds::domain::DomainParticipant::assert_liveliness, or by calling dds::pub::DataWriter::assert_liveliness, or dds::pub::DataWriter::write() on any dds::pub::DataWriter belonging to the dds::domain::DomainParticipant. |
MANUAL_BY_TOPIC |
RTI Connext will only assume liveliness of the dds::pub::DataWriter if the application has asserted liveliness of that dds::pub::DataWriter itself. The user application takes responsibility to signal liveliness to RTI Connext using the dds::pub::DataWriter::assert_liveliness method, or by writing some data. |