In order for a DataReader and a DataWriter with the same Topic to communicate, their DDS types must be consistent according to the DataReader’s type-consistency enforcement policy value, defined in its TYPE_CONSISTENCY_ENFORCEMENT QosPolicy). This status indicates that another DomainParticipant has created a Topic using the same name as the local Topic, but with an inconsistent DDS type.
The status is a structure of type DDS_InconsistentTopicStatus, see DDS_InconsistentTopicStatus Structure. The total_count keeps track of the total number of (DataReader, DataWriter) pairs with topic names that match the Topic to which this status is attached, but whose DDS types are inconsistent. The TopicListener’s on_inconsistent_topic() operation is invoked when this status changes (an inconsistent topic is found). You can also retrieve the current value by calling the Topic’s get_inconsistent_topic_status() operation.
The value of total_count_change reflects the number of inconsistent topics that were found since the last time get_inconsistent_topic_status() was called by user code or on_inconsistent_topic() was invoked by Connext DDS.
|
Type |
Field Name |
Description |
|
DDS_Long |
total_count |
Total cumulative count of (DataReader, DataWriter) pairs whose topic names match the Topic to which this status is attached, but whose DDS types are inconsistent. |
|
DDS_Long |
total_count_change |
The change in total_count since the last time this status was read. |
© 2018 RTI