Use these QoS fields to configure how samples are ordered when stored and accessed by a DataReader.

Basic Settings


com.rti.dds.infrastructure.DestinationOrderQosPolicy	kind
	<<basic>> <<spec>> Specifies the desired kind of destination order.

Advanced Settings


com.rti.dds.infrastructure.PresentationQosPolicy	access_scope
	<<spec>> Determines the largest scope spanning the entities for which the order and coherency of changes can be preserved.

com.rti.dds.infrastructure.PresentationQosPolicy	coherent_access
	<<spec>> Specifies support for coherent access. Controls whether coherent access is supported within the scope `access_scope`.

com.rti.dds.infrastructure.PresentationQosPolicy	ordered_access
	<<spec>> Specifies support for ordered access to the samples received at the subscription end. Controls whether ordered access is supported within the scope `access_scope`.

com.rti.dds.infrastructure.PresentationQosPolicy	drop_incomplete_coherent_set
	<<extension>> Indicates whether or not a com.rti.dds.subscription.DataReader should drop samples from an incomplete coherent set (one for which not all the samples were received). Such samples are reported as lost in the SAMPLE_LOST Status.

com.rti.dds.infrastructure.DestinationOrderQosPolicy	scope
	<<spec>> Specifies the desired scope of the source destination order.

com.rti.dds.infrastructure.DestinationOrderQosPolicy	source_timestamp_tolerance
	<<extension>> Allowed tolerance between source timestamps of consecutive samples.