old-www/LDP/nag/node16.html

45 lines
1.9 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>The Socket Library</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node17.html"> Networking</A>
<B>Up:</B> <A HREF="node7.html">TCP/IP Networks</A>
<B> Previous:</B> <A HREF="node15.html">More on Ports</A>
<BR> <P>
<H2><A NAME="SECTION003390000">The Socket Library</A></H2>
<A NAME="introtcpipsockets"></A>
In operating systems, the software performing all the tasks and
protocols described above is usually part of the kernel, and so it is in
. The programming interface most common in the world is
the <em>Berkeley Socket Library</em>. Its name derives from a popular
analogy that views ports as sockets, and connecting to a port as
plugging in. It provides the (bind(2)) call to specify a remote
host, a transport protocol, and a service which a program can connect or
listen to (using connect(2), listen(2), and
accept(2)). The socket library is however somewhat more general,
in that it provides not only a class of TCP/IP-based sockets (the
AF_INET sockets), but also a class that handles connections
local to the machine (the AF_UNIX class). Some implementations
can also handle other classes as well, like the XNS (<em>Xerox
Networking System</em>) protocol, or X.25.
<P>
In , the socket library is part of the standard libc
C-library. Currently, it only supports AF_INET and AF_UNIX
sockets, but efforts are made to incorporate support for Novell's
networking protocols, so that eventually one or more socket classes for
these would be added.
<P>
<A NAME="607"></A>
<P>
<BR> <HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>