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::core::policy::Partition	name
	<<basic>> <<spec>> A list of partition names
rti::core::policy::Discovery	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.
rti::core::policy::Discovery	accept_unknown_peers
	<<basic>> <<extension>> Whether to accept a new participant that is not in the initial peers list.
rti::core::policy::Discovery	enable_endpoint_discovery
	[DEPRECATED] <<extension>> Whether to automatically enable endpoint discovery for all the remote participants.
rti::core::policy::DomainParticipantResourceLimits	max_partitions
	<<extension>> Maximum number of partition name strings allowable in a dds::core::policy::Partition.
rti::core::policy::DomainParticipantResourceLimits	max_partition_cumulative_characters
	<<extension>> Maximum number of combined characters allowable in all partition names in a dds::core::policy::Partition.
rti::core::MonitoringDedicatedParticipantSettings	domain_id
	<<basic>> <<extension>> The domain ID used in the creation of RTI Monitoring Library 2.0 dds::domain::DomainParticipant.
rti::core::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 rti::core::MonitoringDistributionSettings::dedicated_participant.