Classes | |
| interface | ShmemTransport |
| Built-in transport plug-in for inter-process communications using shared memory. More... | |
| interface | UDPv4Transport |
| Built-in transport plug-in using UDP/IPv4. More... | |
| interface | UDPv6Transport |
| Built-in transport plug-in using UDP/IPv6. More... | |
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 com.rti.dds.infrastructure.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 com.rti.dds.infrastructure.TransportBuiltinQosPolicy, the plugin is implicitly created and registered to the corresponding com.rti.dds.domain.DomainParticipant by RTI Connext when:
Each builtin transport contains its own set of properties. For example, the 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 the method TransportSupport.set_builtin_transport_property() or by using the PROPERTY QoS policy associated with the com.rti.dds.domain.DomainParticipant. Builtin transport plugin properties specified in com.rti.dds.infrastructure.PropertyQosPolicy always overwrite the ones specified through TransportSupport.set_builtin_transport_property(). 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.
RTI Connext Java API Version 4.5f
Copyright © 17 Mar 2012
Real-Time Innovations, Inc