#include <managed_infrastructure.h>
Static Public Member Functions | |
| static System::String^ | get_discovery_qos_policy_name () |
| Stringified human-readable name for DDS::DiscoveryQosPolicy. | |
Public Attributes | |
| StringSeq^ | enabled_transports |
| The transports available for use by the Discovery mechanism. | |
| StringSeq^ | initial_peers |
| Specifies the multicast group addresses on which discovery-related meta-traffic can be received by the DomainParticipant. | |
| StringSeq^ | multicast_receive_addresses |
| Specifies the multicast group addresses on which discovery-related meta-traffic can be received by the DomainParticipant. | |
| System::Int32 | metatraffic_transport_priority |
| The transport priority to use for the Discovery meta-traffic. | |
Properties | |
| System::Boolean | accept_unknown_peers [get, set] |
| 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.
Only these transports can be used by the discovery mechanism to send meta-traffic via the builtin endpoints (built-in DDS::DataReader and DDS::DataWriter).
Also determines the unicast addresses on which the Discovery mechanism will listen for meta-traffic. These along with the domain_id and participant_id determine the unicast locators on which the Discovery mechanism can receive meta-data.
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.
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).
The 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.
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).
The 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.
| System::Int32 DDS::DiscoveryQosPolicy::metatraffic_transport_priority |
The transport priority to use for the Discovery meta-traffic.
The discovery metatraffic will be sent by the built-in DDS::DataWriter using this transport priority.
[default] 0
System:: Boolean DDS::DiscoveryQosPolicy::accept_unknown_peers [get, set] |
Whether to accept a new participant that is not in the initial peers list.
If false, the participant will only communicate with those in the initial peers list and those added via DDS::DomainParticipant::add_peer().
If true, the participant will also communicate with all discovered remote participants.
Note: If accept_unknown_peers is 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.
[default] true
RTI Data Distribution Service .Net APIs Version 4.5e
Copyright © 23 Oct 2011
Real-Time Innovations, Inc