Discovery Isolation

Use these QoS fields to isolate applications from each other.

Use these QoS fields to isolate applications from each other.

Applications can be isolated through mechanisms such as domain ids, domain tags, and partitions.

See Discovery Overview, in the Core Libraries User's Manual, for more information about discovery.

DDS_PartitionQosPolicy	name
	<<basic>> <<spec>> A list of partition names
DDS_DiscoveryQosPolicy	initial_peers
	<<basic>> <<extension>> Determines the initial list of peers that will be contacted by the Discovery mechanism to send announcements about the presence of this participant.
DDS_DiscoveryQosPolicy	accept_unknown_peers
	<<basic>> <<extension>> Whether to accept a new participant that is not in the initial peers list.
DDS_DiscoveryQosPolicy	enable_endpoint_discovery
	[DEPRECATED] <<extension>> Whether to automatically enable endpoint discovery for all the remote participants.
DDS_DomainParticipantResourceLimitsQosPolicy	max_partitions
	<<extension>> Maximum number of partition name strings allowable in a DDS_PartitionQosPolicy.
DDS_DomainParticipantResourceLimitsQosPolicy	max_partition_cumulative_characters
	<<extension>> Maximum number of combined characters allowable in all partition names in a DDS_PartitionQosPolicy.
DDS_MonitoringDedicatedParticipantSettings	domain_id
	<<basic>> <<extension>> The domain ID used in the creation of RTI Monitoring Library 2.0 DDS_DomainParticipant.
DDS_MonitoringDedicatedParticipantSettings	collector_initial_peers
	<<basic>> <<extension>> Determines the initial list of peers that the discovery process will contact to send announcements about the presence of the DDS_MonitoringDistributionSettings::dedicated_participant.