1 / 12

Chapter 5 Introduction to Windows Socket Recommended reading: Comer, Vol 3, Chapters 4, 5

Dr. Y.W. Leung. 2. The TCP/IP standards do not specify the details of how application software interfaces with TCP/IP protocol software; they only suggest the required functionality.Advantagesflexibility and tolerance for different operating systemsDisadvantagesThe interface details are differen

anson
Télécharger la présentation

Chapter 5 Introduction to Windows Socket Recommended reading: Comer, Vol 3, Chapters 4, 5

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Dr. Y.W. Leung 1 Chapter 5 Introduction to Windows Socket (Recommended reading: Comer, Vol 3, Chapters 4, 5) In most implementations, TCP/IP protocol software is part of the computers system software (e.g., Windows 98, Windows 2000, LINUX). The TCP/IP software operates in a multi-vendor environment. Does not depend on any special vendors internal data representation. Does not use any feature that exists only on a particular computer system. Basically, the software promises to send TCP segments reliably from one source to a destination. too primitive for an application programmer If a programmer is expected to fill up every field in a TCP segment, the programming effort is too unbearable. It is better to have a set of programmer-friendly Application Program Interface (API).

    2. Dr. Y.W. Leung 2 The TCP/IP standards do not specify the details of how application software interfaces with TCP/IP protocol software; they only suggest the required functionality. Advantages flexibility and tolerance for different operating systems Disadvantages The interface details are different for different OSs. Widely used APIs for TCP/IP: Berkeley UNIX socket interface System V UNIX Transport Layer Interface (TLI) Windows Sockets Interface (WinSock, a Windows version of sockets) Interface functionality suggested by TCP/IP Allocate local resources for communication. Specify local and remote communication endpoints. Initiate a connection (client side). Wait for an incoming connection (server side).

    3. Dr. Y.W. Leung 3 Send or receive data. Determine when data arrives. Generate urgent data. Handle incoming urgent data. Terminate a connection gracefully. Handle connection termination from the remote site. Abort communication. Handle error conditions or a connection abort. Release local resources when communication finishes. Socket Interface The socket interface for TCP/IP was first developed on Berkeley UNIX and later ported to other platforms. A socket acts as an endpoint of communication.

    4. Dr. Y.W. Leung 4 The interface is called socket because of the following analogy: Windows Socket Different operating systems have different socket interfaces. In Mircosoft Windows, the socket interface is called Windows Socket, or WinSock, or Windows Socket API (application program interface).

More Related