|
RTI Connext .NET API (legacy)
Version 6.1.1
|
Transport plugins delivered with RTI Connext. More...
Classes | |
| interface | DDS::ShmemTransport |
| Built-in transport plug-in for inter-process communications using shared memory. More... | |
| interface | DDS::UDPv4Transport |
| Transport plug-in using UDP/IPv4. More... | |
| interface | DDS::UDPv4_WAN_Transport |
| Transport plug-in using UDP/IPv4 for WAN communications. More... | |
| interface | DDS::UDPv6Transport |
| Transport plug-in using UDP/IPv6. More... | |
Transport plugins delivered with RTI Connext.
The TRANSPORT_BUILTIN specifies the collection of transport plugins that can be automatically configured and managed by RTI Connext as a convenience to the user.
These transport plugins can simply be turned "on" or "off" by a specifying a bitmask in DDS::TransportBuiltinQosPolicy, thus bypassing the steps for setting up a transport plugin. RTI Connext preconfigures the transport plugin properties, the network address, and the aliases to "factory defined" values.
If a builtin transport plugin is turned "on" in DDS::TransportBuiltinQosPolicy, the plugin is implicitly created and registered to the corresponding DDS::DomainParticipant by RTI Connext when:
whichever happens first.
Each builtin transport contains its own set of properties. For example, the DDS::UDPv4Transport allows the application to specify whether or not multicast is supported, the maximum size of the message, and provides a mechanism for the application to filter out network interfaces.
The builtin transport plugin properties can be changed by using the PROPERTY QoS policy associated with the DDS::DomainParticipant. Refer to the specific builtin transport for the list of property names that can be specified through PROPERTY QoS policy.
Any changes to the builtin transport properties after the builtin transports have been registered with will have no effect.