DDS::TransportUnicastQosPolicy Class Reference

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.

Detailed Description

Specifies a subset of transports and a port number that can be used by an Entity to receive data.

Entity:

DDS::DomainParticipant, DDS::DataReader, DDS::DataWriter

Properties:

RxO = N/A
Changeable = NO

Usage

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).

• For a DDS::DomainParticipant, this QoS policy sets the default list of addresses used by other applications to send user data for local DataReaders.

• For a DDS::DataReader, if set, then other applications will use the specified list of addresses to send user data (and reliable protocol packets for reliable DataReaders). Otherwise, if not set, the other applications will use the addresses set by the DDS::DomainParticipant.

• For a reliable DDS::DataWriter, if set, then other applications will use the specified list of addresses to send reliable protocol packets (ACKS/NACKS) on the behalf of reliable DataReaders. Otherwise, if not set, the other applications will use the addresses set by the DDS::DomainParticipant.

Member Data Documentation

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.

See Also

DDS::DomainParticipantQos::default_unicast