RTI Connext C API Version 7.3.0
|
Specifies a subset of transports and a port number that can be used by an Entity to receive data. More...
Data Fields | |
struct DDS_TransportUnicastSettingsSeq | value |
A sequence of unicast communication settings. More... | |
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 16) 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). Note that this is a hard limit that cannot be increased. However, this limit can be decreased by configuring the 'dds.domain_participant.max_announced_locator_list_size' property in the DDS_PropertyQosPolicy associated with the DDS_DomainParticipantQos.
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 16 addresses will be used.
RTI Connext will create a receive thread for every unique port number that it encounters (on a per transport basis).
struct DDS_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
[default] Empty sequence.