Model Scope and Limitations
The Transport Adaptation Layer (TPAL) model suite presents a basic, uniform interface between applications and transport layer models. All interactions with a remote application through TPAL is organized into sessions. A session is a single conversation between two applications through a transport protocol. (For some transport protocols, a server application may actually receive data from more than one remote host during a single session.)
Note: We use the term application throughout this chapter to describe the process that uses TPAL to access the transport layer, even though in the OSI model there are several layers between the application and the transport.
TPAL also provides a global registry of servers. Each server registers itself at the beginning of the simulation by providing the name of the service, the port index through which it can be accessed, and a “popularity” value, or “selection weight” that indicates how often clients use the service. Client applications can select servers from this registry.
Because TPAL provides a uniform interface to all transport protocols, most features exclusive to a particular transport cannot be used. An example of a protocol-dependent feature not supported by TPAL is the TCP PUSH option.