DDS_TransportUnicastQosPolicy Struct Reference

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

List of all members.

Public Attributes

 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.

DDSDomainParticipant, DDSDataReader, DDSDataWriter
RxO = N/A
Changeable = NO


RTI Data Distribution Service 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 DDSEntity 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 Data Distribution Service will create a receive thread for every unique port number that it encounters (on a per transport basis).

Member Data Documentation

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:

RTI Data Distribution Service C++ API Version 4.5e Copyright © 23 Oct 2011 Real-Time Innovations, Inc