|Shared Memory Transport|
|Built-in transport plug-in for inter-process communications using shared memory (NDDS_TRANSPORT_CLASSID_SHMEM). |
|Built-in transport plug-in using UDP/IPv4 (NDDS_TRANSPORT_CLASSID_UDPv4). |
|Built-in transport plug-in using UDP/IPv6 (NDDS_TRANSPORT_CLASSID_UDPv6). |
The TRANSPORT_BUILTIN specifies the collection of transport plugins that can be automatically configured and managed by RTI Data Distribution Service 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 Data Distribution Service 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 DDSDomainParticipant by RTI Data Distribution Service when:
Each builtin transport contains its own set of properties. For example, the ::UDPv4 Transport 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 NDDSTransportSupport::set_builtin_transport_property() or by using the PROPERTY QoS policy associated with the DDSDomainParticipant. Builtin transport plugin properties specified in DDS_PropertyQosPolicy always overwrite the ones specified through NDDSTransportSupport::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.
Registering a transport with a participant. This is useful when the application needs different values for the network addresses.