RTI Connext Modern C++ API
Version 5.3.0
|
<<extension>> Specifies a subset of transports and a port number that can be used by a dds::core::Entity to receive data. More...
#include <rti/core/policy/CorePolicy.hpp>
Public Member Functions | |
TransportUnicast () | |
Creates the default policy. | |
TransportUnicast (const rti::core::TransportUnicastSettingsSeq &settings) | |
Creates an instance with the specified settings. | |
TransportUnicast & | settings (const rti::core::TransportUnicastSettingsSeq &value) |
Sets the unicast settings. | |
rti::core::TransportUnicastSettingsSeq | settings () const |
Gets the unicast settings. | |
<<extension>> Specifies a subset of transports and a port number that can be used by a dds::core::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::core::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 rti::core::policy::Property associated with the dds::domain::qos::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 rti::core::policy::TransportBuiltin and rti::core::policy::TransportSelection). Also, the associated ports are automatically determined (see rti::core::RtpsWellKnownPorts).
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).
|
inline |
Creates the default policy.
|
explicit |
Creates an instance with the specified settings.
TransportUnicast& rti::core::policy::TransportUnicast::settings | ( | const rti::core::TransportUnicastSettingsSeq & | value | ) |
Sets the unicast settings.
An empty sequence means that applicable defaults specified by elsewhere (e.g. dds::domain::qos::DomainParticipantQos::default_unicast) should be used.
The RTPS wire protocol currently limits the maximum number of unicast locators to 16. 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 rti::core::policy::Property associated with the dds::domain::qos::DomainParticipantQos.
[default] Empty sequence.
rti::core::TransportUnicastSettingsSeq rti::core::policy::TransportUnicast::settings | ( | ) | const |
Gets the unicast settings.