|
RTI Connext Modern C++ API
Version 6.1.0
|
Abstraction of a Transport Plugin network interface. More...
Classes | |
| struct | NDDS_Transport_Interface_t |
| Storage for the description of a network interface used by a Transport Plugin. More... | |
Enumerations | |
| enum | NDDS_Transport_Interface_Status_t { NDDS_TRANSPORT_INTERFACE_OFF = 0, NDDS_TRANSPORT_INTERFACE_ON = 1 } |
| Interface status. More... | |
Abstraction of a Transport Plugin network interface.
A Transport Plugin may be able to use several logical or physical network interfaces in a single node (machine). For example, there may be multiple NICs for IP networks or multiple serial ports for serial networks.
An instance of a Transport Plugin is a conduit to one or more network interfaces associated with the transport.
Instances of a Transport Plugin must assign a unique unicast address to each of the network interfaces that it can use to send and receive messages. The unicast address should be within the range of addresses that are addressible by the Transport Plugin (as defined by the plugin itself).
Then, when RTI Connext sends a message to an unicast destination address, the destination address will be made of two parts. The network address and an interface address. The network address portion will be used by RTI Connext to select the Transport Plugin instance that will send the message. The interface address portion is passed to the Transport Plugin instance as the destination interface to which the message should be sent.