Transport plugins delivered with RTI Connext. 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:

the DDS_DomainParticipant is enabled,
the first DataWriter/DataReader is created, or
you lookup a builtin DataReader (DDS_Subscriber_lookup_datareader),

whichever happens first.

Each builtin transport contains its own set of properties. For example, the ::NDDS_Transport_UDPv4_Plugin 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 function NDDS_Transport_Support_set_builtin_transport_property() or by using the PROPERTY QoS policy associated with the DDS_DomainParticipant. Builtin transport plugin properties specified in DDS_PropertyQosPolicy always overwrite the ones specified through NDDS_Transport_Support_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.

See Also: NDDS_Transport_Support_set_builtin_transport_property() DDS_PropertyQosPolicy

The built-in transport plugins can also be instantiated and registered by the user, following the steps for Registering a transport with a participant. This is useful when the application needs different values for the network addresses.