Built-in Topics

Built-in objects created by RTI Connext but accessible to the application. More...

Modules
	Participant Built-in Topics
	Builtin topic for accessing information about the DomainParticipants discovered by RTI Connext.
	Publication Built-in Topics
	Builtin topic for accessing information about the Publications discovered by RTI Connext.
	Subscription Built-in Topics
	Builtin topic for accessing information about the Subscriptions discovered by RTI Connext.
	Topic Built-in Topics
	Builtin topic for accessing information about the Topics discovered by RTI Connext.
	Common types and functions
	Types and functions related to the built-in topics.

Detailed Description

Built-in objects created by RTI Connext but accessible to the application.

RTI Connext must discover and keep track of the remote entities, such as new participants in the domain. This information may also be important to the application, which may want to react to this discovery, or else access it on demand.

A set of built-in topics and corresponding com.rti.dds.subscription.DataReader objects are introduced to be used by the application to access these discovery information.

The information can be accessed as if it was normal application data. This allows the application to know when there are any changes in those values by means of the com.rti.dds.infrastructure.Listener or the com.rti.dds.infrastructure.Condition mechanisms.

The built-in data-readers all belong to a built-in com.rti.dds.subscription.Subscriber, which can be retrieved by using the method com.rti.dds.domain.DomainParticipant.get_builtin_subscriber. The built-in com.rti.dds.subscription.DataReader objects can be retrieved by using the operation com.rti.dds.subscription.Subscriber.lookup_datareader, with the topic name as a parameter.

Built-in entities have default listener settings as well. The built-in com.rti.dds.subscription.Subscriber and all of its built-in topics have 'nil' listeners with all statuses appearing in their listener masks (acting as a NO-OP listener that does not reset communication status). The built-in DataReaders have null listeners with no statuses in their masks.

The information that is accessible about the remote entities by means of the built-in topics includes all the QoS policies that apply to the corresponding remote Entity. This QoS policies appear as normal 'data' fields inside the data read by means of the built-in Topic. Additional information is provided to identify the Entity and facilitate the application logic.

The built-in com.rti.dds.subscription.DataReader will not provide data pertaining to entities created from the same com.rti.dds.domain.DomainParticipant under the assumption that such entities are already known to the application that created them.

Refer to builtin.ParticipantBuiltinTopicData, builtin.TopicBuiltinTopicData, builtin.SubscriptionBuiltinTopicData and builtin.PublicationBuiltinTopicData for a description of all the built-in topics and their contents.

The QoS of the built-in com.rti.dds.subscription.Subscriber and com.rti.dds.subscription.DataReader objects is given by the following table:

QoS of built-in com.rti.dds.subscription.Subscriber and com.rti.dds.subscription.DataReader

QoS	Value
com.rti.dds.infrastructure.UserDataQosPolicy	0-length sequence
com.rti.dds.infrastructure.TopicDataQosPolicy	0-length sequence
com.rti.dds.infrastructure.GroupDataQosPolicy	0-length sequence
com.rti.dds.infrastructure.DurabilityQosPolicy	com.rti.dds.infrastructure.DurabilityQosPolicyKind.DurabilityQosPolicyKind.TRANSIENT_LOCAL_DURABILITY_QOS
com.rti.dds.infrastructure.DurabilityServiceQosPolicy	Does not apply as com.rti.dds.infrastructure.DurabilityQosPolicyKind is com.rti.dds.infrastructure.DurabilityQosPolicyKind.DurabilityQosPolicyKind.TRANSIENT_LOCAL_DURABILITY_QOS
com.rti.dds.infrastructure.PresentationQosPolicy	access_scope = com.rti.dds.infrastructure.PresentationQosPolicyAccessScopeKind.PresentationQosPolicyAccessScopeKind.TOPIC_PRESENTATION_QOS coherent_access = com.rti.dds.infrastructure.false ordered_access = com.rti.dds.infrastructure.false
com.rti.dds.infrastructure.DeadlineQosPolicy	Period = infinite
com.rti.dds.infrastructure.LatencyBudgetQosPolicy	duration = 0
com.rti.dds.infrastructure.OwnershipQosPolicy	com.rti.dds.infrastructure.OwnershipQosPolicyKind.OwnershipQosPolicyKind.SHARED_OWNERSHIP_QOS
com.rti.dds.infrastructure.OwnershipStrengthQosPolicy	value = 0
com.rti.dds.infrastructure.LivelinessQosPolicy	kind = com.rti.dds.infrastructure.LivelinessQosPolicyKind.LivelinessQosPolicyKind.AUTOMATIC_LIVELINESS_QOS lease_duration = 0
com.rti.dds.infrastructure.TimeBasedFilterQosPolicy	minimum_separation = 0
com.rti.dds.infrastructure.PartitionQosPolicy	0-length sequence
com.rti.dds.infrastructure.ReliabilityQosPolicy	kind = com.rti.dds.infrastructure.ReliabilityQosPolicyKind.ReliabilityQosPolicyKind.RELIABLE_RELIABILITY_QOS max_blocking_time = 100 milliseconds
com.rti.dds.infrastructure.DestinationOrderQosPolicy	com.rti.dds.infrastructure.DestinationOrderQosPolicyKind.DestinationOrderQosPolicyKind.BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS
com.rti.dds.infrastructure.HistoryQosPolicy	kind = com.rti.dds.infrastructure.HistoryQosPolicyKind.HistoryQosPolicyKind.KEEP_LAST_HISTORY_QOS depth = 1
com.rti.dds.infrastructure.ResourceLimitsQosPolicy	max_samples = com.rti.dds.infrastructure.ResourceLimitsQosPolicy.LENGTH_UNLIMITED max_instances = com.rti.dds.infrastructure.ResourceLimitsQosPolicy.LENGTH_UNLIMITED max_samples_per_instance = com.rti.dds.infrastructure.ResourceLimitsQosPolicy.LENGTH_UNLIMITED
com.rti.dds.infrastructure.ReaderDataLifecycleQosPolicy	autopurge_nowriter_samples_delay = infinite autopurge_disposed_samples_delay = infinite
com.rti.dds.infrastructure.EntityFactoryQosPolicy	autoenable_created_entities = com.rti.dds.infrastructure.true