mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-08-03 16:39:00 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Fix typos: despatcher -> dispatcher.

Browse source
This commit is contained in:
Thomas Heller 2002-09-17 15:19:12 +00:00
parent 29275c9331
commit c687401337
2 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

12
Doc/lib/libasynchat.tex
View file

@ -13,26 +13,26 @@ are of variable length. \refmodule{asynchat} defines the abstract class
\class{async_chat} that you subclass, providing implementations of the
\method{collect_incoming_data()} and \method{found_terminator()}
methods. It uses the same asynchronous loop as \refmodule{asyncore}, and
the two types of channel, \class{asyncore.despatcher} and
the two types of channel, \class{asyncore.dispatcher} and
\class{asynchat.async_chat}, can freely be mixed in the channel map.
Typically an \class{asyncore.despatcher} server channel generates new
Typically an \class{asyncore.dispatcher} server channel generates new
\class{asynchat.async_chat} channel objects as it receives incoming
connection requests.
\begin{classdesc}{async_chat}{}
This class is an abstract subclass of \class{asyncore.despatcher}. To make
This class is an abstract subclass of \class{asyncore.dispatcher}. To make
practical use of the code you must subclass \class{async_chat}, providing
meaningful \method{collect_incoming_data()} and \method{found_terminator()}
methods. The \class{asyncore.despatcher} methods can be
methods. The \class{asyncore.dispatcher} methods can be
used, although not all make sense in a message/response context.
Like \class{asyncore.despatcher}, \class{async_chat} defines a set of events
Like \class{asyncore.dispatcher}, \class{async_chat} defines a set of events
that are generated by an analysis of socket conditions after a
\cfunction{select()} call. Once the polling loop has been started the
\class{async_chat} object's methods are called by the event-processing
framework with no action on the part of the programmer.
Unlike \class{asyncore.despatcher}, \class{async_chat} allows you to define
Unlike \class{asyncore.dispatcher}, \class{async_chat} allows you to define
a first-in-first-out queue (fifo) of \emph{producers}. A producer need have
only one method, \method{more()}, which should return data to be transmitted
on the channel. The producer indicates exhaustion (\emph{i.e.} that it contains