RTI Connext C API
Version 5.2.3
|
Indicates the level of reliability offered/requested by RTI Connext. More...
Data Structures | |
struct | DDS_ReliabilityQosPolicy |
Indicates the level of reliability offered/requested by RTI Connext. More... | |
Enumerations | |
enum | DDS_ReliabilityQosPolicyKind { DDS_BEST_EFFORT_RELIABILITY_QOS, DDS_RELIABLE_RELIABILITY_QOS } |
Kinds of reliability. More... | |
enum | DDS_ReliabilityQosPolicyAcknowledgmentModeKind { DDS_PROTOCOL_ACKNOWLEDGMENT_MODE, DDS_APPLICATION_AUTO_ACKNOWLEDGMENT_MODE , DDS_APPLICATION_EXPLICIT_ACKNOWLEDGMENT_MODE } |
Kinds of acknowledgment. More... | |
Variables | |
const char *const | DDS_RELIABILITY_QOS_POLICY_NAME |
Stringified human-readable name for DDS_ReliabilityQosPolicy. | |
Indicates the level of reliability offered/requested by RTI Connext.
Kinds of reliability.
DDS_BEST_EFFORT_RELIABILITY_QOS |
Indicates that it is acceptable to not retry propagation of any samples. Presumably new values for the samples are generated often enough that it is not necessary to re-send or acknowledge any samples. [default] for DDS_DataReader and DDS_Topic |
DDS_RELIABLE_RELIABILITY_QOS |
Specifies RTI Connext will attempt to deliver all samples in its history. Missed samples may be retried. In steady-state (no modifications communicated via the DDS_DataWriter), RTI Connext guarantees that all samples in the DDS_DataWriter history will eventually be delivered to all the DDS_DataReader objects (subject to timeouts that indicate loss of communication with a particular DDS_Subscriber). Outside steady state, the HISTORY and RESOURCE_LIMITS policies will determine how samples become part of the history and whether samples can be discarded from it. [default] for DDS_DataWriter |
Kinds of acknowledgment.
DDS_PROTOCOL_ACKNOWLEDGMENT_MODE |
Samples are acknowledged by RTPS protocol. Samples are acknowledged according to the Real-Time Publish-Subscribe (RTPS) interoperability protocol. |
DDS_APPLICATION_AUTO_ACKNOWLEDGMENT_MODE |
Samples are acknowleged automatically after a subscribing application has accessed them. A sample received by a FooDataReader is acknowledged after it has been taken and then returned. Specifically, all samples taken by a call to FooDataReader_take are acknowledged after FooDataReader_return_loan is called. |
DDS_APPLICATION_EXPLICIT_ACKNOWLEDGMENT_MODE |
Samples are acknowledged after the subscribing application explicitly calls acknowledge on the samples. Samples received by a DDS_DataReader are explicitly acknowledged by the subscribing application, after it calls either DDS_DataReader_acknowledge_all or DDS_DataReader_acknowledge_sample. |
const char* const DDS_RELIABILITY_QOS_POLICY_NAME |
Stringified human-readable name for DDS_ReliabilityQosPolicy.