TransportUnicastQosPolicy Class Reference

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

Inheritance diagram for TransportUnicastQosPolicy:

Public Attributes
final TransportUnicastSettingsSeq	value
	A sequence of unicast communication settings.
Public Attributes inherited from QosPolicy
final QosPolicyId_t	id
	The ID of this QoS policy.
final String	policy_name
	The name of this QoS policy.

Additional Inherited Members
Public Member Functions inherited from Struct
abstract boolean	equals (Object obj)
abstract int	hashCode ()
String	toString ()
Protected Member Functions inherited from Struct
	Struct ()
abstract void	pull_from_nativeI (long native_status)
abstract void	push_to_nativeI (long native_status)

Detailed Description

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

Entity:

com.rti.dds.domain.DomainParticipant, com.rti.dds.subscription.DataReader, com.rti.dds.publication.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 com.rti.dds.infrastructure.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 com.rti.dds.infrastructure.PropertyQosPolicy associated with the com.rti.dds.domain.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 com.rti.dds.infrastructure.TransportBuiltinQosPolicy and com.rti.dds.infrastructure.TransportSelectionQosPolicy). Also, the associated ports are automatically determined (see com.rti.dds.infrastructure.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).

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

• For a com.rti.dds.subscription.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 com.rti.dds.domain.DomainParticipant.

• For a reliable com.rti.dds.publication.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 com.rti.dds.domain.DomainParticipant.

Member Data Documentation

final TransportUnicastSettingsSeq value

A sequence of unicast communication settings.

An empty sequence means that applicable defaults specified by elsewhere (e.g. com.rti.dds.domain.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 com.rti.dds.infrastructure.PropertyQosPolicy associated with the com.rti.dds.domain.DomainParticipantQos.

[default] Empty sequence.

See Also

com.rti.dds.domain.DomainParticipantQos.default_unicast