6. Transport Layer¶
The transport layer provides communication services between DDS entities, being responsible of actually sending and receiving messages over a physical transport. The DDS layer uses this service for both user data and discovery traffic communication. However, the DDS layer itself is transport independent, it defines a transport API and can run over any transport plugin that implements this API. This way, it is not restricted to a specific transport, and applications can choose the one that best suits their requirements, or create their own.
eProsima Fast DDS comes with five transports already implemented:
UDPv4: UDP Datagram communication over IPv4. This transport is created by default on a new DomainParticipant if no specific transport configuration is given (see UDP Transport).
UDPv6: UDP Datagram communication over IPv6 (see UDP Transport).
TCPv4: TCP communication over IPv4 (see TCP Transport).
TCPv6: TCP communication over IPv6 (see TCP Transport).
SHM: Shared memory communication among entities running on the same host. This transport is created by default on a new DomainParticipant if no specific transport configuration is given (see Shared Memory Transport).
Although it is not part of the transport module, intraprocess data delivery and data sharing delivery are also available to send messages between entities on some settings. The figure below shows a comparison between the different transports available in Fast DDS.
- 6.1. Transport API
- 6.2. UDP Transport
- 6.3. TCP Transport
- 6.4. Shared Memory Transport
- 6.5. Data-sharing delivery
- 6.6. Intra-process delivery
- 6.7. TLS over TCP
- 6.8. Listening Locators
- 6.9. Announced Locators
- 6.10. Interface Whitelist
- 6.11. Disabling all Multicast Traffic