RTI Connext C API
Version 6.0.1
|
Specifies the physical transports a DDS_DataWriter or DDS_DataReader may use to send or receive data. More...
Data Fields | |
struct DDS_StringSeq | enabled_transports |
A sequence of transport aliases that specifies the transport instances available for use by the entity. | |
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.
struct DDS_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.
The memory for the strings in this sequence is managed according to the conventions described in 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 installed with and available to the DDS_DomainParticipant.
[range] A sequence of non-null,non-empty strings.