Key to distinguish the discovered DomainParticipant

Data that can be set when the related DomainParticipant is created (via the USER_DATA QosPolicy) and that the application may use as it wishes (e.g., to perform some security checking).

Pairs of names/values to be stored with the DomainParticipant. See PROPERTY QosPolicy (DDS Extension) . The usage is strictly application-dependent.

Version number of the RTPS wire protocol used.

ID of vendor implementing the RTPS wire protocol.

Bitmap set by the discovery plugins.

Each bit in this field indicates a built-in endpoint present for discovery.

If the TransportUnicastQosPolicy is not specified when a DataWriter/DataReader is created, the unicast_locators in the corresponding Publication/Subscription built-in topic data will be empty. When the unicast_locators in the Publication/SubscriptionBuiltinTopicData is empty, the default_unicast_locators in the corresponding Participant Builtin Topic Data is assumed.

If default_unicast_locators is empty, it defaults to DomainParticipantQos.default_unicast.

Vendor-specific parameter. The current version of Connext DDS.

Name and role_name assigned to the DomainParticipant. See ENTITY_NAME QosPolicy (DDS Extension).

Domain ID associated with the discovered participant.

A sequence of DDS_TransportInfo_t containing information about each of the installed transports of the discovered DomainParticipant.

A DDS_TransportInfo_t structure contains the class_id and message_size_max for a single transport.

The maximum length of this sequence is controlled by the DOMAIN_PARTICIPANT_RESOURCE_LIMITS QosPolicy (DDS Extension) transport_info_list_max_length (see DDS_DomainParticipantResourceLimitsQosPolicy ).

Connext DDS uses the transport information propagated via discovery to detect potential misconfigurations in a Connext DDS distributed system. If two DomainParticipants that discover each other have one common transport with different values for message_size_max, Connext DDS prints a warning message about that condition.

Key to distinguish the discovered DataWriter

Key to distinguish the participant to which the discovered DataWriter belongs

Topic name of the discovered DataWriter

Type name attached to the topic of the discovered DataWriter

QosPolicies of the discovered DataWriter

Data that can be set when the DataWriter is created (via the USER_DATA QosPolicy) and that the application may use as it wishes.

QosPolicies of the discovered DataWriter

Name of the partition, set in the PARTITION QosPolicy for the publisher to which the discovered DataWriter belongs

Data that can be set when the Topic (with which the discovered DataWriter is associated) is created (via the TOPIC_DATA QosPolicy) and that the application may use as it wishes.

Data that can be set when the Publisher to which the discovered DataWriter belongs is created (via the GROUP_DATA QosPolicy) and that the application may use as it wishes.

Describes the type of the remote DataReader.

See the API Reference HTML documentation.

Type code information about this Topic. See Using Generated Types without Connext DDS (Standalone) .

The key of the Publisher to which the DataWriter belongs.

Properties (pairs of names/values) assigned to the corresponding DataWriter. Usage is strictly application-dependent. See PROPERTY QosPolicy (DDS Extension) .

If the TransportUnicastQosPolicy is not specified when a DataWriter/DataReader is created, the unicast_locators in the corresponding Publication/Subscription built-in topic data will be empty. When the unicast_locators in the Publication/SubscriptionBuiltinTopicData is empty, the default_unicast_locators in the corresponding Participant Builtin Topic Data is assumed.

Virtual GUID for the corresponding DataWriter. For more information, see Durability and Persistence Based on Virtual GUIDs.

Service associated with the discovered DataWriter.

Version number of the RTPS wire protocol in use.

ID of the vendor implementing the RTPS wire protocol.

Vendor-specific value. For RTI, this is the current version of Connext DDS.

When the MULTI_CHANNEL QosPolicy (DDS Extension) is used on the discovered DataWriter, the locator_filter contains the sequence of LocatorFilters in that policy.

There is one LocatorFilter per DataWriter channel. A channel is defined by a filter expression and a sequence of multicast locators.

See LOCATOR_FILTER QoS Policy (DDS Extension).

Vendor specific parameter. Determines whether matching DataReaders send positive acknowledgements for reliability.

Key to distinguish the discovered DataReader.

Key to distinguish the participant to which the discovered DataReader belongs.

Topic name of the discovered DataReader.

Type name attached to the Topic of the discovered DataReader.

QosPolicies of the discovered DataReader

Data that can be set when the DataReader is created (via the USER_DATA QosPolicy) and that the application may use as it wishes.

QosPolicies of the discovered DataReader

Name of the partition, set in the PARTITION QosPolicy for the Subscriber to which the discovered DataReader belongs.

Data that can be set when the Topic to which the discovered DataReader belongs is created (via the TOPIC_DATA QosPolicy) and that the application may use as it wishes.

Data that can be set when the Publisher to which the discovered DataReader belongs is created (via the GROUP_DATA QosPolicy) and that the application may use as it wishes.

Describes the type of the remote DataReader.

See the API Reference HTML documentation.

Indicates the type-consistency requirements of the remote DataReader. See TYPE_CONSISTENCY_ENFORCEMENT QosPolicy and the RTI Connext DDS Core Libraries Getting Started Guide Addendum for Extensible Types.

Type code information about this Topic. See Using Generated Types without Connext DDS (Standalone) .

Key of the Subscriber to which the DataReader belongs.

Properties (pairs of names/values) assigned to the corresponding DataReader. Usage is strictly application-dependent. See PROPERTY QosPolicy (DDS Extension) .

If the TransportUnicastQosPolicy is not specified when a DataWriter/DataReader is created, the unicast_locators in the corresponding Publication/Subscription builtin topic data will be empty. When the unicast_locators in the Publication/SubscriptionBuiltinTopicData is empty, the default_unicast_locators in the corresponding Participant Builtin Topic Data is assumed.

Custom multicast locators that the endpoint can specify.

Provides all the required information to enable content filtering on the writer side.

Virtual GUID for the corresponding DataReader. For more information, see Durability and Persistence Based on Virtual GUIDs.

Service associated with the discovered DataReader.

Version number of the RTPS wire protocol in use.

ID of the vendor implementing the RTPS wire protocol.

Vendor-specific value. For RTI, this is the current version of Connext DDS.

Vendor specific parameter. Determines whether matching DataReaders send positive acknowledgements for reliability.

Key to distinguish the discovered Topic

Topic name

type name attached to the Topic

QosPolicy of the discovered Topic

period = infinite

kind = BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS

kind = TRANSIENT_LOCAL_DURABILITY_QOS

autoenable_created_entities = TRUE

value = empty sequence

kind = KEEP_LAST_HISTORY_QOS

depth = 1

duration = 0

kind = AUTOMATIC_LIVELINESS_QOS

lease_duration = infinite

kind = SHARED_OWNERSHIP_QOS

value = 0

access_scope = TOPIC_PRESENTATION_QOS

coherent_access = FALSE

ordered_access = FALSE

name = empty sequence

autopurge_nowriter_samples_delay = infinite

kind = RELIABLE_RELIABILITY_QOS

max_blocking_time is irrelevant for the DataReader

Depends on setting of DomainParticipantResourceLimitsQosPolicy and DiscoveryConfigQosPolicy in DomainParticipantQos:

max_samples = domainParticipantQos.discovery_config.
[participant/publication/subscription]_reader_resource_limits.max_samples

max_instances = domainParticipantQos.resource_limits.
[remote_writer/reader/participant]_allocation.max_count

max_samples_per_instance = 1

minimum_separation = 0

value = empty sequence