mirror of https://github.com/python/cpython
Fix typos: despatcher -> dispatcher.
This commit is contained in:
parent
29275c9331
commit
c687401337
|
@ -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
|
||||
|
|
|
@ -59,7 +59,7 @@ service) is closed.
|
|||
-- make sure you extend, rather than override, \method{__init__()}
|
||||
if you want to retain this behavior).
|
||||
|
||||
Channels (instances of \class{asyncore.despatcher}, \class{asynchat.async_chat}
|
||||
Channels (instances of \class{asyncore.dispatcher}, \class{asynchat.async_chat}
|
||||
and subclasses thereof) can freely be mixed in the map.
|
||||
\end{funcdesc}
|
||||
|
||||
|
|
Loading…
Reference in New Issue