RELIABILITY

Indicates the level of reliability offered/requested by RTI Connext DDS Micro. More...

Data Structures
struct	DDS_ReliabilityQosPolicy
	<<cert>> Indicates the level of reliability offered/requested by RTI Connext DDS Micro. More...

Enumerations
enum	DDS_ReliabilityQosPolicyKind { DDS_BEST_EFFORT_RELIABILITY_QOS , DDS_RELIABLE_RELIABILITY_QOS }
	Kinds of reliability. More...

Detailed Description

Indicates the level of reliability offered/requested by RTI Connext DDS Micro.

Enumeration Type Documentation

DDS_ReliabilityQosPolicyKind

enum DDS_ReliabilityQosPolicyKind

Kinds of reliability.

QoS:

DDS_ReliabilityQosPolicy

Enumerator
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]
DDS_RELIABLE_RELIABILITY_QOS	Specifies RTI Connext DDS Micro will attempt to deliver all samples in its history. Missed samples may be retried. In steady-state (no modifications communicated via the DDS_DataWriter) the middleware 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. NOTE: The RTPS spec defines reliability as 0x03 to comply with RTPS spec. However, RTI Connext Core uses 0x3, as well as others.