RTI Connext .NET API (legacy)
Version 6.1.2
|
Specifies the physical transports a DDS::DataWriter or DDS::DataReader may use to send or receive data. More...
#include <managed_infrastructure.h>
Static Public Member Functions | |
static System::String ^ | get_transportselection_qos_policy_name () |
Stringified human-readable name for DDS::TransportSelectionQosPolicy. More... | |
Public Attributes | |
StringSeq ^ | enabled_transports |
A sequence of transport aliases that specifies the transport instances available for use by the entity. More... | |
Specifies the physical transports a DDS::DataWriter or DDS::DataReader may use to send or receive data.
An application may be simultaneously connected to many different physical transports, e.g., Ethernet, Infiniband, shared memory, VME backplane, and wireless. By default, RTI Connext will use up to 16 transports to deliver data from a DataWriter to a DataReader.
This QoS policy can be used to both limit and control which of the application's available transports may be used by a DDS::DataWriter to send data or by a DDS::DataReader to receive data.
StringSeq ^ DDS::TransportSelectionQosPolicy::enabled_transports |
A sequence of transport aliases that specifies the transport instances available for use by the entity.
Of the transport instances installed with the DDS::DomainParticipant, only those with aliases matching an alias in this sequence are available to the entity.
Thus, this list of aliases sub-selects from the transports available to the DDS::DomainParticipant.
An empty sequence is a special value that specifies all the transports installed with the DDS::DomainParticipant.
Alias names for the builtin transports are defined in TRANSPORT_BUILTIN. These alias names are case sensitive and should be written in lowercase.
[default] Empty sequence; i.e. all the transports installed with and available to the DDS::DomainParticipant.
[range] A sequence of non-null,non-empty strings.