|
RTI Connext C API Version 7.6.0
|
Use these QoS fields to configure how samples are ordered when stored and accessed by a DataReader.
Use these QoS fields to configure how samples are ordered when stored and accessed by a DataReader.
Basic Settings
| DDS_DestinationOrderQosPolicy | kind |
| <<basic>> <<spec>> Specifies the desired kind of destination order. | |
Advanced Settings
| DDS_PresentationQosPolicy | access_scope |
| <<spec>> Determines the largest scope spanning the entities for which the order and coherency of changes can be preserved. | |
| DDS_PresentationQosPolicy | coherent_access |
<<spec>> Specifies support for coherent access. Controls whether coherent access is supported within the scope access_scope. | |
| DDS_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. | |
| DDS_PresentationQosPolicy | drop_incomplete_coherent_set |
| <<extension>> Indicates whether or not a DDS_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. | |
| DDS_DestinationOrderQosPolicy | scope |
| <<spec>> Specifies the desired scope of the source destination order. | |
| DDS_DestinationOrderQosPolicy | source_timestamp_tolerance |
| <<extension>> Allowed tolerance between source timestamps of consecutive samples. | |