<html lang="en"> <head> <title>Networking - SBCL 1.0.31 User Manual</title> <meta http-equiv="Content-Type" content="text/html"> <meta name="description" content="SBCL 1.0.31 User Manual"> <meta name="generator" content="makeinfo 4.13"> <link title="Top" rel="start" href="index.html#Top"> <link rel="prev" href="Timers.html#Timers" title="Timers"> <link rel="next" href="Profiling.html#Profiling" title="Profiling"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- This manual is part of the SBCL software system. See the `README' file for more information. This manual is largely derived from the manual for the CMUCL system, which was produced at Carnegie Mellon University and later released into the public domain. This manual is in the public domain and is provided with absolutely no warranty. See the `COPYING' and `CREDITS' files for more information. --> <meta http-equiv="Content-Style-Type" content="text/css"> <style type="text/css"><!-- pre.display { font-family:inherit } pre.format { font-family:inherit } pre.smalldisplay { font-family:inherit; font-size:smaller } pre.smallformat { font-family:inherit; font-size:smaller } pre.smallexample { font-size:smaller } pre.smalllisp { font-size:smaller } span.sc { font-variant:small-caps } span.roman { font-family:serif; font-weight:normal; } span.sansserif { font-family:sans-serif; font-weight:normal; } --></style> </head> <body> <div class="node"> <a name="Networking"></a> <p> Next: <a rel="next" accesskey="n" href="Profiling.html#Profiling">Profiling</a>, Previous: <a rel="previous" accesskey="p" href="Timers.html#Timers">Timers</a>, Up: <a rel="up" accesskey="u" href="index.html#Top">Top</a> <hr> </div> <!-- node-name, next, previous, up --> <h2 class="chapter">14 Networking</h2> <p><a name="index-Sockets_002c-Networking-517"></a> The <code>sb-bsd-sockets</code> module provides a thinly disguised BSD socket API for SBCL. Ideas have been stolen from the BSD socket API for C and Graham Barr's IO::Socket classes for Perl. <p>Sockets are represented as CLOS objects, and the API naming conventions attempt to balance between the BSD names and good lisp style. <ul class="menu"> <li><a accesskey="1" href="Sockets-Overview.html#Sockets-Overview">Sockets Overview</a> <li><a accesskey="2" href="General-Sockets.html#General-Sockets">General Sockets</a>: Methods applicable to all sockets <li><a accesskey="3" href="Socket-Options.html#Socket-Options">Socket Options</a> <li><a accesskey="4" href="INET-Domain-Sockets.html#INET-Domain-Sockets">INET Domain Sockets</a> <li><a accesskey="5" href="Local-_0028Unix_0029-Domain-Sockets.html#Local-_0028Unix_0029-Domain-Sockets">Local (Unix) Domain Sockets</a> <li><a accesskey="6" href="Name-Service.html#Name-Service">Name Service</a> </ul> </body></html>