LIVELINESS

Determines the mechanism and parameters used by the application to determine whether a DDSEntity is alive. More...

Classes
struct	DDS_LivelinessQosPolicy
	<<cert>> Determines the mechanism and parameters used by the application to determine whether a DDSEntity is alive. More...

Enumerations
enum	DDS_LivelinessQosPolicyKind { DDS_AUTOMATIC_LIVELINESS_QOS, DDS_MANUAL_BY_PARTICIPANT_LIVELINESS_QOS, DDS_MANUAL_BY_TOPIC_LIVELINESS_QOS }
	Kinds of liveliness. More...

Variables
const char *const	DDS_LIVELINESS_QOS_POLICY_NAME
	Stringified human-readable name for DDS_LivelinessQosPolicy.

---

Detailed Description

Determines the mechanism and parameters used by the application to determine whether a DDSEntity is alive.

---

Enumeration Type Documentation

enum DDS_LivelinessQosPolicyKind

Kinds of liveliness.

QoS:

DDS_LivelinessQosPolicy

Enumerator:

DDS_AUTOMATIC_LIVELINESS_QOS	[default] The infrastructure will automatically signal liveliness for the DDSDataWriter (s) at least as often as required by the DDSDataWriter (S) lease_duration. A DDSDataWriter with this setting does not need to take any specific action in order to be considered 'alive.' The DDSDataWriter 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. Only DDS_DURATION_INFINITE is supported for lease_duration. Finite lease_duration is not supported with this liveliness setting.
DDS_MANUAL_BY_PARTICIPANT_LIVELINESS_QOS	RTI Connext Micro will assume that as long as at least one DDSDataWriter belonging to the DDSDomainParticipant (or the DDSDomainParticipant itself) has asserted its liveliness, then the other DataWriters belonging to that same DDSDomainParticipant are also alive. Only DDS_DURATION_INFINITE is supported for lease_duration. Finite lease_duration is not supported with this liveliness setting. The user application takes responsibility to signal liveliness to RTI Connext Micro by calling DDSDataWriter::assert_liveliness, or FooDataWriter::write on any DDSDataWriter belonging to the DDSDomainParticipant.
DDS_MANUAL_BY_TOPIC_LIVELINESS_QOS	RTI Connext Micro will only assume liveliness of the DDSDataWriter if the application has asserted liveliness of that DDSDataWriter itself. The user application takes responsibility to signal liveliness to RTI Connext Micro using the DDSDataWriter::assert_liveliness method, or by writing some data.

---

Variable Documentation

const char* const DDS_LIVELINESS_QOS_POLICY_NAME

Stringified human-readable name for DDS_LivelinessQosPolicy.