|The transports available for use by the Discovery mechanism. |
|Determines the initial list of peers that will be contacted by the Discovery mechanism to send announcements about the presence of this participant. |
|Specifies the multicast group addresses on which discovery-related meta-traffic can be received by the DomainParticipant. |
|The transport priority to use for the Discovery meta-traffic. |
|Whether to accept a new participant that is not in the initial peers list. |
The middleware will periodically send network packets to these locations, announcing itself to any remote applications that may be present, and will listen for announcements from those applications.
This QoS policy is an extension to the DDS standard.
The transports available for use by the Discovery mechanism.
Also determines the unicast addresses on which the Discovery mechanism will listen for meta-traffic. These along with the
participant_id determine the unicast locators on which the Discovery mechanism can receive meta-data.
The memory for the strings in this sequence is managed according to the conventions described in Conventions. In particular, be careful to avoid a situation in which RTI Data Distribution Service allocates a string on your behalf and you then reuse that string in such a way that RTI Data Distribution Service believes it to have more memory allocated to it than it actually does.
Alias names for the builtin transports are defined in TRANSPORT_BUILTIN.
[default] Empty sequence. All the transports available to the DomainParticipant are available for use by the Discovery mechanism.
[range] Sequence of non-null,non-empty strings.
Determines the initial list of peers that will be contacted by the Discovery mechanism to send announcements about the presence of this participant.
If there is a remote peer DDSDomainParticipant such as is described in this list, it will become aware of this participant and will engage in the Discovery protocol to exchange meta-data with this participant.
Each element of this list must be a
peer descriptor in the proper format (see Peer Descriptor Format).
[default] See NDDS_DISCOVERY_PEERS
[range] Sequence of arbitrary length.
Specifies the multicast group addresses on which discovery-related meta-traffic can be received by the DomainParticipant.
The multicast group addresses on which the Discovery mechanism will listen for meta-traffic.
Each element of this list must be a valid multicast address (IPv4 or IPv6) in the proper format (see Address Format).
domain_id determines the multicast port on which the Discovery mechanism can receive meta-data.
If NDDS_DISCOVERY_PEERS does not contain a multicast address, then the string sequence DDS_DiscoveryQosPolicy::multicast_receive_addresses is cleared and the RTI discovery process will not listen for discovery messages via multicast.
If NDDS_DISCOVERY_PEERS contains one or more multicast addresses, the addresses will be stored in DDS_DiscoveryQosPolicy::multicast_receive_addresses, starting at element 0. They will be stored in the order they appear NDDS_DISCOVERY_PEERS.
Note: Currently, RTI Data Distribution Service will only listen for discovery traffic on the first multicast address (element 0) in DDS_DiscoveryQosPolicy::multicast_receive_addresses.
[default] See NDDS_DISCOVERY_PEERS
[range] Sequence of length [0,1], whose elements are multicast addresses. Currently only the first multicast address (if any) is used. The rest are ignored.
The transport priority to use for the Discovery meta-traffic.
The discovery metatraffic will be sent by the built-in DDSDataWriter using this transport priority.
Whether to accept a new participant that is not in the initial peers list.
If DDS_BOOLEAN_TRUE, the participant will also communicate with all discovered remote participants.
Note: If accept_unknown_peers is DDS_BOOLEAN_FALSE and shared memory is disabled, applications on the same node will not communicate if only 'localhost' is specified in the peers list. If shared memory is disabled or 'shmem://' is not specified in the peers list, to communicate with other applications on the same node through the loopback interface, you must put the actual node address or hostname in NDDS_DISCOVERY_PEERS.