RTI Connext C API Version 7.2.0

Specifies the behavior of RTI Connext in the case where the value of an instance changes (one or more times) before it can be successfully communicated to one or more existing subscribers. More...

Data Structures

struct  DDS_HistoryQosPolicy
 Specifies the behavior of RTI Connext in the case where the value of a sample changes (one or more times) before it can be successfully communicated to one or more existing subscribers. More...
 

Enumerations

enum  DDS_HistoryQosPolicyKind {
  DDS_KEEP_LAST_HISTORY_QOS ,
  DDS_KEEP_ALL_HISTORY_QOS
}
 Kinds of history. More...
 

Variables

const char *const DDS_HISTORY_QOS_POLICY_NAME
 Stringified human-readable name for DDS_HistoryQosPolicy. More...
 

Detailed Description

Specifies the behavior of RTI Connext in the case where the value of an instance changes (one or more times) before it can be successfully communicated to one or more existing subscribers.

Enumeration Type Documentation

◆ DDS_HistoryQosPolicyKind

Kinds of history.

QoS:
DDS_HistoryQosPolicy
Enumerator
DDS_KEEP_LAST_HISTORY_QOS 

[default] Keep the last depth samples.

On the publishing side, RTI Connext will only attempt to keep the most recent depth samples of each instance of data (identified by its key) managed by the DDS_DataWriter. Invalid samples representing a disposal or unregistration of an instance count towards the depth and may replace other DDS samples currently in the DataWriter queue for the same instance.

On the subscribing side, the DDS_DataReader will only attempt to keep the most recent depth samples received for each instance (identified by its key) until the application takes them via the DDS_DataReader 's take() operation.
Invalid samples representing a disposal or unregistration of an instance do not count towards the history depth and will not replace other DDS samples currently in the DataReader queue for the same instance.

DDS_KEEP_ALL_HISTORY_QOS 

Keep all the samples.

On the publishing side, RTI Connext will attempt to keep all samples (representing each value written) of each instance of data (identified by its key) managed by the DDS_DataWriter until they can be delivered to all subscribers.

On the subscribing side, RTI Connext will attempt to keep all samples of each instance of data (identified by its key) managed by the DDS_DataReader. These samples are kept until the application takes them from RTI Connext via the take() operation.

Variable Documentation

◆ DDS_HISTORY_QOS_POLICY_NAME

const char* const DDS_HISTORY_QOS_POLICY_NAME
extern

Stringified human-readable name for DDS_HistoryQosPolicy.