Transport Protocol Types

TIBCO FTL software supports several transport types, each characterized by the protocols it uses to establish a bus and to transfer message data.

• Dynamic TCP Transport
  A dynamic TCP (DTCP) transport bus establishes a set of TCP connections dynamically, decoupling the transport definitions from specific hosts and ports. You can use dynamic TCP transports to easily specify a variety of communication topologies. A DTCP transport can be server-based or peer-to-peer.
• Static TCP Transport
  A static TCP transport communicates over a set of dedicated connections. A static TCP transport can be server-based or peer-to-peer.
• Auto Transport
  An Auto transport bus, like a DTCP transport, establishes a set of TCP connections dynamically, decoupling the transport definitions from specific hosts and ports. However, with an Auto transport, In the simplest configuration, you don't need to specify listen or connect ports; a transport name is all that is required. An Auto transport can only be server-based and is typically used for persistence service transports, eftl service transports, and group server transports. One main difference between DTCP transport and Auto transport is that DTCP transports require additional ports to be open if running behind a load balancer or a firewall, whereas Auto transports redirect all communication via the FTL Server port.
• Multicast Transport (mcast)
  A multicast transport is a peer-to-peer transport that carries reliable multicast communication among endpoints on many host computers. Multicast transports are efficient for high fan-out communication across a LAN.
• Process Transport (PROC)
  Endpoints within a single program process can communicate using a process (PROC) transport. Process transports are peer-to-peer transports that communicate at high speeds and exhibit very low latency.
• Shared Memory Transport
  Endpoints in programs that run on the same host computer can communicate using a shared memory transport. Shared memory transports are peer-to-peer transports that communicate at high speeds and exhibit very low latency.
• Direct Shared Memory Transport
  Direct publishers and direct subscribers can use a direct shared memory transport to communicate within the same host computer. Direct shared memory transports are peer-to-peer transports similar to shared memory transports, with some additional restrictions. They communicate at high speeds and exhibit extremely low latency.
• Reliable UDP Transport (RUDP)
  A reliable UDP (RUDP) transport is a peer-to-peer transport that carries reliable communication over a set of dedicated connections. Endpoints on an RUDP bus exchange UDP datagrams. RUDP transports use a positive acknowledgement protocol for reliable message transfer.
• Remote Direct Memory Access Transport (RDMA)
  On computers that support remote direct memory access (RDMA), network adapters can move data directly from memory in one computer to memory in another computer across a network. This strategy can reduce or eliminate several sources of latency resulting from overhead, including network protocol overhead, operating system overhead, and context switching overhead.