RTI Connext Traditional C++ API  Version 7.0.0

Type representing a list of unicast locators. More...

Public Attributes

struct DDS_StringSeq transports
 A sequence of transport aliases that specifies the unicast interfaces on which to receive unicast traffic for the entity. More...
 
DDS_Long receive_port
 The unicast port on which the entity can receive data. More...
 

Detailed Description

Type representing a list of unicast locators.

A unicast locator specifies a transport class, a unicast address, and a unicast port number on which messages can be received by an entity.

QoS:
DDS_TransportUnicastQosPolicy

Member Data Documentation

◆ transports

struct DDS_StringSeq DDS_TransportUnicastSettings_t::transports

A sequence of transport aliases that specifies the unicast interfaces on which to receive unicast traffic for the entity.

Of the transport instances available to the entity, only those with aliases matching an alias on this sequence are used to determine the unicast interfaces used by the entity.

Thus, this list of aliases sub-selects from the transports available to the entity.

Each unicast interface on a transport results in a unicast locator for the entity.

An empty sequence is a special value that specifies all the transports available to the entity.

The memory for the strings in this sequence is managed according to the conventions described in String Conventions. In particular, be careful to avoid a situation in which RTI Connext allocates a string on your behalf and you then reuse that string in such a way that RTI Connext 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; i.e. all the transports available to the entity.
[range] Any sequence of non-null, non-empty strings.

◆ receive_port

DDS_Long DDS_TransportUnicastSettings_t::receive_port

The unicast port on which the entity can receive data.

Must be an unused unicast port on the system.

[default] 0, which implies that the actual port number is determined by a formula as a function of the domain_id, and the DDS_WireProtocolQosPolicy::participant_id.

[range] [0,0xffffffff]

See also
DDS_WireProtocolQosPolicy::participant_id.