[issue2006] asyncore loop lacks timers and work tasks

[Bill Janssen]

Bill Janssen added the comment:

Sorry, I meant to say, "so things without input FDs can make progress".

On Feb 6, 2008 8:08 PM, Bill Janssen <bill.janssen at gmail.com> wrote:

> Yes, that's it exactly.  So things without work tasks can still get done.
>
> But timers are the important thing.  With timers you can always implement
> work tasks by yourself.
>
>
> On Feb 6, 2008 12:49 PM, Giampaolo Rodola' <report at bugs.python.org> wrote:
>
> >
> > Giampaolo Rodola' added the comment:
> >
> > I still don't get it.  Maybe you're talking about something like "call a
> > function at the next select() loop" which in Twisted is equal to:
> > >>> reactor.callLater(0, something)
> >
> > By using my patched asyncore you can do the same with:
> > >>> self.call_later(0, something)
> >
> > __________________________________
> > Tracker <report at bugs.python.org>
> > <http://bugs.python.org/issue2006>
> > __________________________________
> >
>
>

Added file: http://bugs.python.org/file9373/unnamed

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue2006>
__________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: unnamed
Url: http://mail.python.org/pipermail/python-bugs-list/attachments/20080207/37c65b42/attachment.txt