Scribd
Upload
24 views

12 - Network Programming With Windows Socket

This document discusses using Windows Sockets (Winsock) for network programming. Winsock allows programs to communicate over TCP/IP networks following industry standards, enabling interoperability between Windows and non-Windows systems. It shows how to modify an existing client/server program to use the Winsock API for networked interprocess communication in a more standard, portable way compared to other Windows IPC mechanisms.

Uploaded by

Henra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
24 views

12 - Network Programming With Windows Socket

This document discusses using Windows Sockets (Winsock) for network programming. Winsock allows programs to communicate over TCP/IP networks following industry standards, enabling interoperability between Windows and non-Windows systems. It shows how to modify an existing client/server program to use the Winsock API for networked interprocess communication in a more standard, portable way compared to other Windows IPC mechanisms.

Uploaded by

Henra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Network Programming with

Windows Socket
• Named pipes and mailslots are suitable for interprocess
communication between processes on the same computer
or processes on Windows computers connected by a local
or wide area network.
• Named pipes and mailslots (both simply referred to here as
“named pipes” unless the distinction is important) have the
distinct drawback, however, of not being an industry
standard.
• The resulting system can operate over TCP/IP-based wide
area networks, and the server, for instance, can accept
requests from UNIX, Linux, and other non-Windows clients.
• Windows provides interoperability by
supporting Windows Sockets, which are nearly
the same as, and interoperable with, Berkeley
Sockets, a de facto industry standard.
• This chapter shows how to use the Windows
Sockets (or “Winsock”) API by modifying
Chapter 11’s client/server system.
Winsock
• Winsock, by enabling standards-based
interoperability, allows programmers to
exploit higher-level protocols and applications,
such as ftp, http, RPCs, and COM, all of which
provide different, and higher-level, models for
standard, interoperable, networked
interprocess communication.
• Winsock, because of conformance to industry
standards, has naming conventions and
programming characteristics somewhat different
from the Windows functions described so far. The
Winsock API is not strictly a part of the Windows API.
• Winsock also provides additional functions that are
not part of the standard; these functions are used
only as absolutely required. Among other
advantages, programs will be more portable to other
operating systems.
Socket Server Functions

• In this discussion, a server is a process that


accepts connections on a specified port. While
sockets, like named pipes, can be used for
peer-to-peer communication, this distinction
is convenient and reflects the manner in which
two machines connect to one another.

You might also like