Previous Topic: TCP/IP Socket ConnectionsNext Topic: Target Server Environment Communication Styles


Client Manager to Server Configuration

The Client Manager TCP/IP implementation makes use of stream sockets. A stream socket provides a full-duplex, sequenced, reliable transmission mechanism over which a DPC cooperative flow request can be transmitted. The socket provides the TCP communications endpoint, used by the Client Manager, to gain access to the IP network.

A target server environment, which is connected to the IP network, listens for inbound connections and data transmissions using a socket that is located on the system hosting the target server.

A socket, used by the Client Manager, consists of two parts, each defining application endpoints in the TCP communications. One of the application endpoints is the local application (that is, the Client Manager). The other endpoint is the socket processing that supports the given target server environment. These front-end connection management processes for a given server execution environment are as follows:

Each connection that a client TCP application establishes on a given workstation is identified by its unique TCP port address. When a connection to a target server is requested, the source port address is selected by TCP from those port numbers not already in use by other TCP connections currently established. The destination port address is the target server environment well-known port address. The target server IP address, along with its port address, is used by the Client Manager in the construction of the destination portion of the TCP socket.