DESTINATION_ORDER
[QoS Policies]

Controls the criteria used to determine the logical order among changes made by DDSPublisher entities to the same instance of data (i.e., matching DDSTopic and key). More...

Classes
struct	DDS_DestinationOrderQosPolicy
	Controls how the middleware will deal with data sent by multiple DDSDataWriter entities for the same instance of data (i.e., same DDSTopic and key). More...
Enumerations
enum	DDS_DestinationOrderQosPolicyKind {   DDS_BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS,   DDS_BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS }
	Kinds of destination order. More...
Variables
const char *const	DDS_DESTINATIONORDER_QOS_POLICY_NAME
	Stringified human-readable name for DDS_DestinationOrderQosPolicy.

---

Detailed Description

Controls the criteria used to determine the logical order among changes made by DDSPublisher entities to the same instance of data (i.e., matching DDSTopic and key).

---

Enumeration Type Documentation

enum DDS_DestinationOrderQosPolicyKind

Kinds of destination order.

QoS:

DDS_DestinationOrderQosPolicy

Enumerator:

DDS_BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS	[default] Indicates that data is ordered based on the reception time at each DDSSubscriber. Since each subscriber may receive the data at different times there is no guaranteed that the changes will be seen in the same order. Consequently, it is possible for each subscriber to end up with a different final value for the data.
DDS_BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS	Indicates that data is ordered based on a time-stamp placed at the source (by RTI Connext or by the application). In any case this guarantees a consistent final value for the data in all subscribers. See also: Special Instructions if Using 'Timestamp' APIs and BY_SOURCE_TIMESTAMP Destination Ordering:

---

Variable Documentation

const char* const DDS_DESTINATIONORDER_QOS_POLICY_NAME

Stringified human-readable name for DDS_DestinationOrderQosPolicy.