|
RTI Connext Traditional C++ API
Version 6.0.0
|
Controls how a DDSDataWriter handles the lifecycle of the instances (keys) that it is registered to manage. More...
Public Attributes | |
| DDS_Boolean | autodispose_unregistered_instances |
| Boolean flag that controls the behavior when the DDSDataWriter unregisters an instance by means of the unregister operations. | |
| struct DDS_Duration_t | autopurge_unregistered_instances_delay |
| <<extension>> Maximum duration for which the DDSDataWriter will maintain information regarding an instance once it has unregistered the instance. | |
| struct DDS_Duration_t | autopurge_disposed_instances_delay |
| <<extension>> Maximum duration for which the DDSDataWriter will maintain information regarding an instance once it has disposed the instance. | |
Controls how a DDSDataWriter handles the lifecycle of the instances (keys) that it is registered to manage.
This policy determines how the DDSDataWriter acts with regards to the lifecycle of the data instances it manages (data instances that have been either explicitly registered with the DDSDataWriter or implicitly registered by directly writing the data).
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 DDSDataWriter is deleted either directly by means of the DDSPublisher::delete_datawriter operation or indirectly as a consequence of calling DDSPublisher::delete_contained_entities or DDSDomainParticipant::delete_contained_entities that contains the DataWriter.
You may use FooDataWriter::unregister_instance to indicate that the DDSDataWriter no longer wants to send data for a DDSTopic.
The behavior controlled by this QoS policy applies on a per instance (key) basis for keyed Topics, so that when a DDSDataWriter unregisters an instance, RTI Connext 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.
| DDS_Boolean DDS_WriterDataLifecycleQosPolicy::autodispose_unregistered_instances |
Boolean flag that controls the behavior when the DDSDataWriter unregisters an instance by means of the unregister operations.
dispose operations on the instance prior to calling the unregister operation. [default] DDS_BOOLEAN_TRUE
| struct DDS_Duration_t DDS_WriterDataLifecycleQosPolicy::autopurge_unregistered_instances_delay |
<<extension>> Maximum duration for which the DDSDataWriter will maintain information regarding an instance once it has unregistered the instance.
Determines how long the DDSDataWriter will maintain information regarding an instance that has been unregistered. By default, the DDSDataWriter resources associated with an instance (e.g., the space needed to remember the Instance Key or KeyHash) are released lazily. This means the resources are only reclaimed when the space is needed for another instance because DDS_ResourceLimitsQosPolicy::max_instances is exceeded. This behavior can be changed by setting autopurge_unregistered_instances_delay to a value other than DDS_DURATION_INFINITE.
After this time elapses, the DDSDataWriter will purge all internal information regarding the instance, including historical samples, even if DDS_ResourceLimitsQosPolicy::max_instances has not been reached.
The purging of unregistered instances can be done based on the source tiemstamp of the unregister sample or the time where the unregister sample was added to the DataWriter queue by setting the following property to 1 or 0 respectively:
dds.data_writer.history.source_timestamp_based_autopurge_instances_delay
The default value for the property is 0.
This QoS value is not supported with durable DDSDataWriter queues.
[default] DDS_DURATION_INFINITE (disabled) for all DDSDataWriter except for the built-in discovery DataWriters DDS_DURATION_ZERO for built-in discovery DataWriters (see DDS_DiscoveryConfigQosPolicy::publication_writer_data_lifecycle and DDS_DiscoveryConfigQosPolicy::subscription_writer_data_lifecycle).
[range] [0, 1 year] or DDS_DURATION_INFINITE
| struct DDS_Duration_t DDS_WriterDataLifecycleQosPolicy::autopurge_disposed_instances_delay |
<<extension>> Maximum duration for which the DDSDataWriter will maintain information regarding an instance once it has disposed the instance.
Determines how long the DDSDataWriter will maintain information regarding an instance that has been disposed of. By default, disposing of an instance does not make it eligible to be purged. By setting autopurge_disposed_instances_delay to a value other than DDS_DURATION_INFINITE, the DataWriter will delete the resources associated with an instance (including historical samples) once the time has elapsed and all matching DataReaders have acknowledged all the samples for this instance including the dispose sample.
The purging of disposed instances can be done based on the source timestamp of the dispose sample or the time when the dispose sample was added to the DataWriter queue by setting the following property to 1 or 0 respectively:
dds.data_writer.history.source_timestamp_based_autopurge_instances_delay
The default value for the property is 0.
This QoS value is supported with durable DataWriter queues only for 0 and INFINITE values (finite values are not supported).
[default] DDS_DURATION_INFINITE (disabled)
[range] [0, 1 year] or DDS_DURATION_INFINITE
RTI Connext Traditional C++ API Version 6.0.0
Copyright © Sun Mar 3 2019
Real-Time Innovations, Inc