#include <managed_infrastructure.h>
Static Public Member Functions | |
static System::String^ | get_writerdatalifecycle_qos_policy_name () |
Stringified human-readable name for DDS::WriterDataLifecycleQosPolicy. | |
Public Attributes | |
Duration_t | autopurge_unregistered_instances_delay |
<<eXtension>> Maximum duration for which the DDS::DataWriter will maintain information regarding an instance once it has unregistered the instance. | |
Properties | |
System::Boolean | autodispose_unregistered_instances [get, set] |
Boolean flag that controls the behavior when the DDS::DataWriter unregisters an instance by means of the unregister operations. |
Since the deletion of a DataWriter automatically unregisters all data instances it manages, the setting of the autodispose_unregistered_instances
flag will only determine whether instances are ultimately disposed when the DDS::DataWriter is deleted either directly by means of the DDS::Publisher::delete_datawriter operation or indirectly as a consequence of calling DDS::Publisher::delete_contained_entities or DDS::DomainParticipant::delete_contained_entities that contains the DataWriter.
You may use DDS::TypedDataWriter::unregister_instance to indicate that the DDS::DataWriter no longer wants to send data for a DDS::Topic.
The behavior controlled by this QoS policy applies on a per instance (key) basis for keyed Topics, so that when a DDS::DataWriter unregisters an instance, RTI Data Distribution Service can automatically also dispose that instance. This is the default behavior.
In many cases where the ownership of a Topic is shared (see DDS::OwnershipQosPolicy), DataWriters may want to relinquish their ownership of a particular instance of the Topic to allow other DataWriters to send updates for the value of that instance regardless of Ownership Strength. In that case, you may only want a DataWriter to unregister an instance without disposing the instance. Disposing an instance is a statement that an instance no longer exists. User applications may be coded to trigger on the disposal of instances, thus the ability to unregister without disposing may be useful to properly maintain the semantic of disposal.
<<eXtension>> Maximum duration for which the DDS::DataWriter will maintain information regarding an instance once it has unregistered the instance.
After this time elapses, the DDS::DataWriter will purge all internal information regarding the instance, including historical samples.
When the duration is zero, the instance is purged as soon as all the samples have been acknowledged by all the live DataReaders.
[default] DDS::Duration_t::DURATION_INFINITE (disabled)
[range] [0, 1 year] or DDS::Duration_t::DURATION_INFINITE
System::Boolean DDS::WriterDataLifecycleQosPolicy::autodispose_unregistered_instances [get, set] |
Boolean flag that controls the behavior when the DDS::DataWriter unregisters an instance by means of the unregister operations.
dispose
operations on the instance prior to calling the unregister
operation.
The DDS::DataWriter will not dispose the instance. The application can still call one of the dispose
operations prior to unregistering the instance and accomplish the same effect.
[default] true