Fixed unresolved reference problem; this module wasn't \label{}ed.

Remove spurious underscore following book title.  Added specific reference to
a Win32 networking book.

Changed \indexsubitem from (in module SocketServer) to (SocketServer protocol),
since it's talking about a protocol supported by a collection of classes.
This commit is contained in:
Fred Drake 1997-12-04 14:36:52 +00:00
parent 98b032a7c0
commit 0d3b4f8beb
2 changed files with 10 additions and 8 deletions

View File

@ -1,8 +1,9 @@
\section{Standard Module \sectcode{SocketServer}} \section{Standard Module \sectcode{SocketServer}}
\label{module-SocketServer}
\stmodindex{SocketServer} \stmodindex{SocketServer}
The \code{SocketServer} module simplifies the task of writing network The \code{SocketServer} module simplifies the task of writing network
servers. servers.
There are four basic server classes: \code{TCPServer} uses the There are four basic server classes: \code{TCPServer} uses the
Internet TCP protocol, which provides for continuous streams of data Internet TCP protocol, which provides for continuous streams of data
@ -12,8 +13,8 @@ lost while in transit. The more infrequently used
\code{UnixStreamServer} and \code{UnixDatagramServer} classes are \code{UnixStreamServer} and \code{UnixDatagramServer} classes are
similar, but use Unix domain sockets; they're not available on similar, but use Unix domain sockets; they're not available on
non-Unix platforms. For more details on network programming, consult non-Unix platforms. For more details on network programming, consult
a book such as W. Richard Steven's \emph{Unix Network Programming}_ or a book such as W. Richard Steven's \emph{UNIX Network Programming}
XXX (a Windows equivalent). or Ralph Davis's \emph{Win32 Network Programming}.
These four classes process requests \dfn{synchronously}; each request These four classes process requests \dfn{synchronously}; each request
must be completed before the next request can be started. This isn't must be completed before the next request can be started. This isn't
@ -36,7 +37,7 @@ many requests.
Server classes have the same external methods and attributes, no Server classes have the same external methods and attributes, no
matter what network protocol they use: matter what network protocol they use:
\renewcommand{\indexsubitem}{(in module SocketServer)} \renewcommand{\indexsubitem}{(SocketServer protocol)}
%XXX should data and methods be intermingled, or separate? %XXX should data and methods be intermingled, or separate?
% how should the distinction between class and instance variables be % how should the distinction between class and instance variables be

View File

@ -1,8 +1,9 @@
\section{Standard Module \sectcode{SocketServer}} \section{Standard Module \sectcode{SocketServer}}
\label{module-SocketServer}
\stmodindex{SocketServer} \stmodindex{SocketServer}
The \code{SocketServer} module simplifies the task of writing network The \code{SocketServer} module simplifies the task of writing network
servers. servers.
There are four basic server classes: \code{TCPServer} uses the There are four basic server classes: \code{TCPServer} uses the
Internet TCP protocol, which provides for continuous streams of data Internet TCP protocol, which provides for continuous streams of data
@ -12,8 +13,8 @@ lost while in transit. The more infrequently used
\code{UnixStreamServer} and \code{UnixDatagramServer} classes are \code{UnixStreamServer} and \code{UnixDatagramServer} classes are
similar, but use Unix domain sockets; they're not available on similar, but use Unix domain sockets; they're not available on
non-Unix platforms. For more details on network programming, consult non-Unix platforms. For more details on network programming, consult
a book such as W. Richard Steven's \emph{Unix Network Programming}_ or a book such as W. Richard Steven's \emph{UNIX Network Programming}
XXX (a Windows equivalent). or Ralph Davis's \emph{Win32 Network Programming}.
These four classes process requests \dfn{synchronously}; each request These four classes process requests \dfn{synchronously}; each request
must be completed before the next request can be started. This isn't must be completed before the next request can be started. This isn't
@ -36,7 +37,7 @@ many requests.
Server classes have the same external methods and attributes, no Server classes have the same external methods and attributes, no
matter what network protocol they use: matter what network protocol they use:
\renewcommand{\indexsubitem}{(in module SocketServer)} \renewcommand{\indexsubitem}{(SocketServer protocol)}
%XXX should data and methods be intermingled, or separate? %XXX should data and methods be intermingled, or separate?
% how should the distinction between class and instance variables be % how should the distinction between class and instance variables be