Builtin Transport Plugins
There are two ways in which the builtin transport plugins may be registered:
- Default builtin Transport Instances: Builtin transports that are turned "on" in the TRANSPORT_BUILTIN QosPolicy (DDS Extension) are implicitly registered when (a) the DomainParticipant is enabled, (b) the first DataWriter/DataReader is created, or (c) you look up a builtin DataReader (by calling lookup_datareader() on a Subscriber), whichever happens first. The builtin transport plugins have default properties. If you want to change these properties, do so before the transports are registered.
- Other Transport Instances: There are two ways to install non-default builtin transport instances:
To configure the properties of the builtin transports:
or
For other builtin transport instances:
- If the builtin transport plugin is created with NDDS_Transport_UDPv4_new(), NDDS_Transport_UDPv6_new() or NDDS_Transport_Shmem_new(), properties can be specified during creation time. See Explicitly Creating Builtin Transport Plugin Instances.
- If the additional builtin transport instances are installed through the PROPERTY QosPolicy (DDS Extension) , the properties of the builtin transport plugins can also be specified through that same QosPolicy.
© 2017 RTI