Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
c6874013
Commit
c6874013
authored
Sep 17, 2002
by
Thomas Heller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos: despatcher -> dispatcher.
parent
29275c93
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
7 deletions
+7
-7
Doc/lib/libasynchat.tex
Doc/lib/libasynchat.tex
+6
-6
Doc/lib/libasyncore.tex
Doc/lib/libasyncore.tex
+1
-1
No files found.
Doc/lib/libasynchat.tex
View file @
c6874013
...
...
@@ -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.d
e
spatcher
}
and
the two types of channel,
\class
{
asyncore.d
i
spatcher
}
and
\class
{
asynchat.async
_
chat
}
, can freely be mixed in the channel map.
Typically an
\class
{
asyncore.d
e
spatcher
}
server channel generates new
Typically an
\class
{
asyncore.d
i
spatcher
}
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.d
e
spatcher
}
. To make
This class is an abstract subclass of
\class
{
asyncore.d
i
spatcher
}
. 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.d
e
spatcher
}
methods can be
methods. The
\class
{
asyncore.d
i
spatcher
}
methods can be
used, although not all make sense in a message/response context.
Like
\class
{
asyncore.d
e
spatcher
}
,
\class
{
async
_
chat
}
defines a set of events
Like
\class
{
asyncore.d
i
spatcher
}
,
\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.d
e
spatcher
}
,
\class
{
async
_
chat
}
allows you to define
Unlike
\class
{
asyncore.d
i
spatcher
}
,
\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
...
...
Doc/lib/libasyncore.tex
View file @
c6874013
...
...
@@ -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.d
e
spatcher
}
,
\class
{
asynchat.async
_
chat
}
Channels (instances of
\class
{
asyncore.d
i
spatcher
}
,
\class
{
asynchat.async
_
chat
}
and subclasses thereof) can freely be mixed in the map.
\end{funcdesc}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment