TCPIPPartII分析.pptVIP

Netprog 2002 - Client/Server Issues TCP/IP Part II Based on Notes by D. Hollinger Based on UNIX Network Programming, Stevens, Chapters 7,11,21,22,27 Also Java Network Programming and Distributed Computing, Chapter 6 Also Online Java Tutorial, Sun. Topics Issues in Client/Server Programming Advanced TCP/IP Options Sample Application-layer Protocols TELNET FTP Issues in Client Programming Identifying the Server. Looking up an IP address. Looking up a well known port name. Specifying a local IP address. UDP client design. TCP client design. Identifying the Server Options: hard-coded into the client program. require that the user identify the server. read from a configuration file. use a separate protocol/network service to lookup the identity of the server. Identifying a TCP/IP server. Need an IP address, protocol and port. We often use host names instead of IP addresses. usually the protocol (UDP vs. TCP) is not specified by the user. often the port is not specified by the user. Services and Ports Many services are available via “well known” addresses (names). There is a mapping of service names to port numbers. Specifying a Local Address When a client creates and binds a socket it must specify a local port and IP address. Typically a client doesn’t care what port it is on: mySocket = new DatagramSocket() Local IP address A client can also ask the operating system to take care of specifying the local IP address: myAddress = InetAddress.getLocalHost(); UDP Client Design Establish server address (IP and port). Allocate a socket. Specify that any valid local port and IP address can be used. Communicate with server (send, receive) Close the socket. Connected mode UDP A UDP client can call connect(address, port) to establish the address of the server. “connect” is a misnomer: A UDP client using a connected mode socket can only talk to that server (using the connected-mode socket). TCP Client Design Establish server address (IP and port). Allocate a socket. Specif