RetroSearch Browse

Thu Mar 5 22:09:20 CET 2009 · http://mail.python.org/pipermail/python-dev/2009-March/086808.html

Josiah Carlson <josiah.carlson at gmail.com> wrote:

> On Thu, Mar 5, 2009 at 12:46 PM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> > Daniel Stutzbach wrote:
> >
> >> If you have a working select(), it will tell you the sockets on which
> >> read() and write() won't block, so non-blocking reads and writes are not
> >> necessary.
> >
> > No, but there should be an interface that lets you say
> > "when something comes in on this fd, call this function
> > for me".
> >
> > In other words it should be a light wrapper around
> > select/poll/whatever that provides a callback interface.
> 
> A read callback, a write callback.  What about close, error, connect,
> and accept callbacks?
> 
> I hate to say it (not really), but that's pretty much the handle_*()
> methods of asyncore :/ .

What asyncore was missing was a timer API (a way to register functions
to be called periodically).  Then it would be pretty much like any other
event loop system.

Bill

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-March/086808.html below:

[Python-Dev] asyncore fixes in Python 2.6 broke Zope's version of medusa