RTI Connext .NET API (legacy)  Version 6.1.0

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

Classes

struct  DDS::DestinationOrderQosPolicy
 Controls how the middleware will deal with data sent by multiple DDS::DataWriter entities for the same instance of data (i.e., same DDS::Topic and key). More...
 

Enumerations

enum  DDS::DestinationOrderQosPolicyKind : UINT32 {
  DDS::DestinationOrderQosPolicyKind::BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS,
  DDS::DestinationOrderQosPolicyKind::BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS
}
 Kinds of destination order. More...
 
enum  DDS::DestinationOrderQosPolicyScopeKind : UINT32 {
  DDS::DestinationOrderQosPolicyScopeKind::INSTANCE_SCOPE_DESTINATIONORDER_QOS,
  DDS::DestinationOrderQosPolicyScopeKind::TOPIC_SCOPE_DESTINATIONORDER_QOS
}
 Scope of source destination order. More...
 

Functions

static System::String ^ DDS::DestinationOrderQosPolicy::get_destinationorder_qos_policy_name ()
 Stringified human-readable name for DDS::DestinationOrderQosPolicy. More...
 

Detailed Description

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

Enumeration Type Documentation

◆ DestinationOrderQosPolicyKind

enum DDS::DestinationOrderQosPolicyKind : UINT32
strong

Kinds of destination order.

QoS:
DDS::DestinationOrderQosPolicy
Enumerator
BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS 

[default] Indicates that data is ordered based on the reception time at each DDS::Subscriber.

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.

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.

Note: If Batching is needed along with BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS and DDS::DestinationOrderQosPolicyScopeKind::INSTANCE_SCOPE_DESTINATIONORDER_QOS, then the DDS::BatchQosPolicy::source_timestamp_resolution and DDS::BatchQosPolicy::thread_safe_write setting of DDS::BatchQosPolicy should be set to DDS::Duration_t::DURATION_ZERO and true respectively.

See also
PublisherDeleteDataWriter_warning

◆ DestinationOrderQosPolicyScopeKind

Scope of source destination order.

QoS:
DDS::DestinationOrderQosPolicy
Enumerator
INSTANCE_SCOPE_DESTINATIONORDER_QOS 

[default] Indicates that data is ordered on a per instance basis if used along with BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS.

The source timestamp of the current sample is compared to the source timestamp of the previously received sample for the same instance. The tolerance check is also applied per instance.

TOPIC_SCOPE_DESTINATIONORDER_QOS 

Indicates that data is ordered on a per topic basis if used along with BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS.

The source timestamp of the current sample is compared to the source timestamp of the previously received sample for the same topic. The tolerance check is also applied per topic.

Function Documentation

◆ get_destinationorder_qos_policy_name()

static System::String ^ DDS::DestinationOrderQosPolicy::get_destinationorder_qos_policy_name ( )
inlinestatic

Stringified human-readable name for DDS::DestinationOrderQosPolicy.