#include <managed_infrastructure.h>
Static Public Member Functions | |
| static System::String^ | get_reliability_qos_policy_name () |
| Stringified human-readable name for DDS::ReliabilityQosPolicy. | |
Public Attributes | |
| ReliabilityQosPolicyKind | kind |
| Kind of reliability. | |
| Duration_t | max_blocking_time |
| The maximum time a writer may block on a write() call. | |
The reliability of a connection between a DataWriter and DataReader is entirely user configurable. It can be done on a per DataWriter/DataReader connection. A connection may be configured to be "best effort" which means that RTI Data Distribution Service will not use any resources to monitor or guarantee that the data sent by a DataWriter is received by a DataReader.
For some use cases, such as the periodic update of sensor values to a GUI displaying the value to a person, DDS::ReliabilityQosPolicyKind::BEST_EFFORT_RELIABILITY_QOS delivery is often good enough. It is certainly the fastest, most efficient, and least resource-intensive (CPU and network bandwidth) method of getting the newest/latest value for a topic from DataWriters to DataReaders. But there is no guarantee that the data sent will be received. It may be lost due to a variety of factors, including data loss by the physical transport such as wireless RF or even Ethernet.
However, there are data streams (topics) in which you want an absolute guarantee that all data sent by a DataWriter is received reliably by DataReaders. This means that RTI Data Distribution Service must check whether or not data was received, and repair any data that was lost by resending a copy of the data as many times as it takes for the DataReader to receive the data. RTI Data Distribution Service uses a reliability protocol configured and tuned by these QoS policies: DDS::HistoryQosPolicy, DDS::DataWriterProtocolQosPolicy, DDS::DataReaderProtocolQosPolicy, and DDS::ResourceLimitsQosPolicy.
The Reliability QoS policy is simply a switch to turn on the reliability protocol for a DataWriter/DataReader connection. The level of reliability provided by RTI Data Distribution Service is determined by the configuration of the aforementioned QoS policies.
You can configure RTI Data Distribution Service to deliver all data in the order they were sent (also known as absolute or strict reliability). Or, as a tradeoff for less memory, CPU, and network usage, you can choose a reduced level of reliability where only the last N values are guaranteed to be delivered reliably to DataReaders (where N is user-configurable). In the reduced level of reliability, there are no guarantees that the data sent before the last N are received. Only the last N data packets are monitored and repaired if necessary.
These levels are ordered, DDS::ReliabilityQosPolicyKind::BEST_EFFORT_RELIABILITY_QOS < DDS::ReliabilityQosPolicyKind::RELIABLE_RELIABILITY_QOS. A DDS::DataWriter offering one level is implicitly offering all levels below.
The setting of this policy has a dependency on the setting of the RESOURCE_LIMITS policy. In case the reliability kind is set to DDS::ReliabilityQosPolicyKind::RELIABLE_RELIABILITY_QOS the write operation on the DDS::DataWriter may block if the modification would cause data to be lost or else cause one of the limits in specified in the RESOURCE_LIMITS to be exceeded. Under these circumstances, the RELIABILITY max_blocking_time configures the maximum duration the write operation may block.
If the DDS::ReliabilityQosPolicy::kind is set to DDS::ReliabilityQosPolicyKind::RELIABLE_RELIABILITY_QOS, data samples originating from a single DDS::DataWriter cannot be made available to the DDS::DataReader if there are previous data samples that have not been received yet due to a communication error. In other words, RTI Data Distribution Service will repair the error and resend data samples as needed in order to reconstruct a correct snapshot of the DDS::DataWriter history before it is accessible by the DDS::DataReader.
If the DDS::ReliabilityQosPolicy::kind is set to DDS::ReliabilityQosPolicyKind::BEST_EFFORT_RELIABILITY_QOS, the service will not re-transmit missing data samples. However, for data samples originating from any one DataWriter the service will ensure they are stored in the DDS::DataReader history in the same order they originated in the DDS::DataWriter. In other words, the DDS::DataReader may miss some data samples, but it will never see the value of a data object change from a newer value to an older value.
kind >= requested kind evaluates to 'TRUE'. For the purposes of this inequality, the values of DDS::ReliabilityQosPolicy::kind are considered ordered such that DDS::ReliabilityQosPolicyKind::BEST_EFFORT_RELIABILITY_QOS < DDS::ReliabilityQosPolicyKind::RELIABLE_RELIABILITY_QOS. Kind of reliability.
[default] DDS::ReliabilityQosPolicyKind::BEST_EFFORT_RELIABILITY_QOS for DDS::DataReader and DDS::Topic, DDS::ReliabilityQosPolicyKind::RELIABLE_RELIABILITY_QOS for DDS::DataWriter
The maximum time a writer may block on a write() call.
This setting applies only to the case where DDS::ReliabilityQosPolicy::kind = DDS::ReliabilityQosPolicyKind::RELIABLE_RELIABILITY_QOS. DDS::TypedDataWriter::write is allowered to block if the DDS::DataWriter does not have space to store the value written. Only applies to DDS::DataWriter.
[default] 100 milliseconds
[range] [0,1 year] or DDS::Duration_t::DURATION_INFINITE
RTI Data Distribution Service .Net APIs Version 4.5c
Copyright © 9 Jun 2010
Real-Time Innovations, Inc