RTI Connext Modern C++ API
Version 5.2.0
|
The definition of the dds::core::safe_enum DurabilityKind. More...
#include <PolicyKind.hpp>
Public Types | |
enum | type { VOLATILE, TRANSIENT_LOCAL, TRANSIENT, PERSISTENT } |
The underlying enum type. More... | |
The definition of the dds::core::safe_enum DurabilityKind.
The underlying enum
type.
VOLATILE |
[default] RTI Connext does not need to keep any samples of data instances on behalf of any dds::sub::DataReader that is unknown by the dds::pub::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. |
TRANSIENT_LOCAL |
RTI Connext will attempt to keep some samples so that they can be delivered to any potential late-joining dds::sub::DataReader. Which particular samples are kept depends on other QoS such as dds::core::policy::History and dds::core::policy::ResourceLimits. RTI Connext is only required to keep the data in memory of the dds::pub::DataWriter that wrote the data. Data is not required to survive the dds::pub::DataWriter. For this setting to be effective, you must also set the dds::core::policy::Reliability::kind to rti::core::policy::ReliabilityKind::RELIABLE. This option does not require RTI Persistence Service. |
TRANSIENT |
RTI Connext will attempt to keep some samples so that they can be delivered to any potential late-joining dds::sub::DataReader. Which particular samples are kept depends on other QoS such as dds::core::policy::History and dds::core::policy::ResourceLimits. 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::pub::DataWriter. Data will survive the dds::pub::DataWriter. This option requires RTI Persistence Service. |
PERSISTENT |
Data is kept on permanent storage, so that they can outlive a system session. This option requires RTI Persistence Service. |