RTI Connext .Net APIs
Version 5.2.0
|
Specifies a subset of transports and a port number that can be used by an Entity to receive data. More...
#include <managed_infrastructure.h>
Static Public Member Functions | |
static System::String^ | get_transportunicast_qos_policy_name () |
Stringified human-readable name for DDS::TransportUnicastQosPolicy. | |
Public Attributes | |
TransportUnicastSettingsSeq^ | value |
A sequence of unicast communication settings. | |
Specifies a subset of transports and a port number that can be used by an Entity to receive data.
RTI Connext may send data to a variety of Entities, not just DataReaders. For example, reliable DataWriters may receive ACK/NACK packets from reliable DataReaders.
During discovery, each DDS::Entity announces to remote applications a list of (up to 4) unicast addresses to which the remote application should send data (either user data packets or reliable protocol meta-data such as ACK/NACKs and heartbeats).
By default, the list of addresses is populated automatically with values obtained from the enabled transport plug-ins allowed to be used by the Entity (see DDS::TransportBuiltinQosPolicy and DDS::TransportSelectionQosPolicy). Also, the associated ports are automatically determined (see DDS::RtpsWellKnownPorts_t).
Use this QoS policy to manually set the receive address list for an Entity. You may optionally set a port to use a non-default receive port as well. Only the first 4 addresses will be used.
RTI Connext will create a receive thread for every unique port number that it encounters (on a per transport basis).
TransportUnicastSettingsSeq ^ DDS::TransportUnicastQosPolicy::value |
A sequence of unicast communication settings.
An empty sequence means that applicable defaults specified by elsewhere (e.g. DDS::DomainParticipantQos::default_unicast) should be used.
The RTPS wire protocol currently limits the maximum number of unicast locators to four.
[default] Empty sequence.