RTI Connext C API
Version 5.2.0
|
This QoS policy specifies whether or not RTI Connext will store and deliver previously published data samples to new DDS_DataReader entities that join the network later. More...
Data Structures | |
struct | DDS_DurabilityQosPolicy |
This QoS policy specifies whether or not RTI Connext will store and deliver previously published data samples to new DDS_DataReader entities that join the network later. More... | |
Enumerations | |
enum | DDS_DurabilityQosPolicyKind { DDS_VOLATILE_DURABILITY_QOS, DDS_TRANSIENT_LOCAL_DURABILITY_QOS, DDS_TRANSIENT_DURABILITY_QOS, DDS_PERSISTENT_DURABILITY_QOS } |
Kinds of durability. More... | |
Variables | |
const char *const | DDS_DURABILITY_QOS_POLICY_NAME |
Stringified human-readable name for DDS_DurabilityQosPolicy. | |
This QoS policy specifies whether or not RTI Connext will store and deliver previously published data samples to new DDS_DataReader entities that join the network later.
Kinds of durability.
DDS_VOLATILE_DURABILITY_QOS |
[default] RTI Connext does not need to keep any samples of data instances on behalf of any DDS_DataReader that is unknown by the DDS_DataWriter at the time the instance is written. In other words, RTI Connext will only attempt to provide the data to existing subscribers. This option does not require RTI Persistence Service. |
DDS_TRANSIENT_LOCAL_DURABILITY_QOS |
RTI Connext will attempt to keep some samples so that they can be delivered to any potential late-joining DDS_DataReader. Which particular samples are kept depends on other QoS such as DDS_HistoryQosPolicy and DDS_ResourceLimitsQosPolicy. RTI Connext is only required to keep the data in memory of the DDS_DataWriter that wrote the data. Data is not required to survive the DDS_DataWriter. For this setting to be effective, you must also set the DDS_ReliabilityQosPolicy::kind to DDS_RELIABLE_RELIABILITY_QOS. This option does not require RTI Persistence Service. |
DDS_TRANSIENT_DURABILITY_QOS |
RTI Connext will attempt to keep some samples so that they can be delivered to any potential late-joining DDS_DataReader. Which particular samples are kept depends on other QoS such as DDS_HistoryQosPolicy and DDS_ResourceLimitsQosPolicy. RTI Connext is only required to keep the data in memory and not in permanent storage. Data is not tied to the lifecycle of the DDS_DataWriter. Data will survive the DDS_DataWriter. This option requires RTI Persistence Service. |
DDS_PERSISTENT_DURABILITY_QOS |
Data is kept on permanent storage, so that they can outlive a system session. This option requires RTI Persistence Service. |
const char* const DDS_DURABILITY_QOS_POLICY_NAME |
Stringified human-readable name for DDS_DurabilityQosPolicy.