|The virtual GUID (Global Unique Identifier).
|The RTPS Object ID.
|Specifies whether this DataReader expects inline QoS with every sample.
|Whether the reader sends positive acknowledgements to writers.
|Indicates whether or not an instance can move to the DDS_NOT_ALIVE_DISPOSED_INSTANCE_STATE state without being in the DDS_ALIVE_INSTANCE_STATE state.
|The reliable protocol defined in RTPS.
DDS has a standard protocol for packet (user and meta data) exchange between applications using DDS for communications. This QoS policy and DDS_DataReaderProtocolQosPolicy give you control over configurable portions of the protocol, including the configuration of the reliable data delivery mechanism of the protocol on a per DataWriter or DataReader basis.
These configuration parameters control timing, timeouts, and give you the ability to tradeoff between speed of data loss detection and repair versus network and CPU bandwidth used to maintain reliability.
It is important to tune the reliability protocol (on a per DDSDataWriter and DDSDataReader basis) to meet the requirements of the end-user application so that data can be sent between DataWriters and DataReaders in an efficient and optimal manner in the presence of data loss.
You can also use this QoS policy to control how RTI Data Distribution Service responds to "slow" reliable DataReaders or ones that disconnect or are otherwise lost. See DDS_ReliabilityQosPolicy for more information on the per-DataReader/DataWriter reliability configuration. DDS_HistoryQosPolicy and DDS_ResourceLimitsQosPolicy also play an important role in the DDS reliable protocol.
This QoS policy is an extension to the DDS standard.
The RTPS Object ID.
This value is used to determine the RTPS object ID of a data reader according to the DDS-RTPS Interoperability Wire Protocol.
Only the last 3 bytes are used; the most significant byte is ignored.
If the default value is specified, RTI Data Distribution Service will automatically assign the object ID based on a counter value (per participant) starting at 0x00800000. That value is incremented for each new data reader.
A rtps_object_id value in the interval [0x00800000,0x00ffffff] may collide with the automatic values assigned by RTI Data Distribution Service. In those cases, the recomendation is not to use automatic object ID assigment.
Specifies whether this DataReader expects inline QoS with every sample.
In RTI Data Distribution Service, a DDSDataReader nominally relies on Discovery to propagate QoS on a matched DDSDataWriter. Alternatively, a DDSDataReader may get information on a matched DDSDataWriter through QoS sent inline with a sample.
Asserting DDS_DataReaderProtocolQosPolicy::expects_inline_qos indicates to a matching DDSDataWriter that this DDSDataReader expects to receive inline QoS with every sample. The complete set of inline QoS that a DDSDataWriter may send inline is specified by the Real-Time Publish-Subscribe (RTPS) Wire Interoperability Protocol.
Because RTI Data Distribution Service DDSDataWriter and DDSDataReader cache Discovery information, inline QoS are largely redundant and thus unecessary. Only for other stateless implementations whose DDSDataReader does not cache Discovery information is inline QoS necessary.
Also note that inline QoS are additional wire-payload that consume additional bandwidth and serialization and deserialization time.
Whether the reader sends positive acknowledgements to writers.
If set to DDS_BOOLEAN_TRUE, the reader does not send positive acknowledgments (ACKs) in response to Heartbeat messages. The reader will send negative acknowledgements (NACKs) when a Heartbeat advertises samples that it has not received.
Otherwise, if set to DDS_BOOLEAN_FALSE (the default), the reader will send ACKs to writers that expect ACKs (DDS_DataWriterProtocolQosPolicy::disable_positive_acks = DDS_BOOLEAN_FALSE) and it will not send ACKs to writers that disable ACKs (DDS_DataWriterProtocolQosPolicy::disable_positive_acks = DDS_BOOLEAN_TRUE)
This field only applies to keyed readers.
When the field is set to DDS_BOOLEAN_TRUE, the DataReader will receive dispose notifications even if the instance is not alive.
To guarantee the key availability through the usage of the API FooDataReader::get_key_value, this option should be used in combination DDS_DataWriterProtocolQosPolicy::serialize_key_with_dispose on the DataWriter that should be set to DDS_BOOLEAN_TRUE.
|struct DDS_RtpsReliableReaderProtocol_t DDS_DataReaderProtocolQosPolicy::rtps_reliable_reader
The reliable protocol defined in RTPS.
[default] min_heartbeat_response_delay 0 seconds; max_heartbeat_response_delay 0.5 seconds