RTI Connext C API
Version 5.2.0
|
Specifies and configures the mechanism that allows DDS_DataReader entities to detect when DDS_DataWriter entities become disconnected or "dead.". More...
Data Structures | |
struct | DDS_LivelinessQosPolicy |
Specifies and configures the mechanism that allows DDS_DataReader entities to detect when DDS_DataWriter entities become disconnected or "dead.". 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. | |
Specifies and configures the mechanism that allows DDS_DataReader entities to detect when DDS_DataWriter entities become disconnected or "dead.".
Kinds of liveliness.
DDS_AUTOMATIC_LIVELINESS_QOS |
[default] The infrastructure will automatically signal liveliness for the DDS_DataWriter (s) at least as often as required by the A DDS_DataWriter with this setting does not need to take any specific action in order to be considered 'alive.' The DDS_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. |
DDS_MANUAL_BY_PARTICIPANT_LIVELINESS_QOS |
RTI Connext will assume that as long as at least one DDS_DataWriter belonging to the DDS_DomainParticipant (or the DDS_DomainParticipant itself) has asserted its liveliness, then the other Entities belonging to that same DDS_DomainParticipant are also alive. The user application takes responsibility to signal liveliness to RTI Connext either by calling DDS_DomainParticipant_assert_liveliness, or by calling DDS_DataWriter_assert_liveliness, or FooDataWriter_write on any DDS_DataWriter belonging to the DDS_DomainParticipant. |
DDS_MANUAL_BY_TOPIC_LIVELINESS_QOS |
RTI Connext will only assume liveliness of the DDS_DataWriter if the application has asserted liveliness of that DDS_DataWriter itself. The user application takes responsibility to signal liveliness to RTI Connext using the DDS_DataWriter_assert_liveliness function, or by writing some data. |
const char* const DDS_LIVELINESS_QOS_POLICY_NAME |
Stringified human-readable name for DDS_LivelinessQosPolicy.