[issue2006] asyncore loop lacks timers and work tasks

[Bill Janssen]

Bill Janssen added the comment:

*I'm not sure to understand what do you mean by "work tasks".*

They're low-priority tasks that need to get run sometime, but aren't
associated with an input source.  In ILU, we had a function called
"do_soon", and you could call it with a function that should be called
sometime in the near future.

*writing a poller suitable with epoll and kqueue*

Christian's patch looks interesting, in that respect.  I haven't applied it
to a codebase yet.

Bill

On Feb 4, 2008 2:00 PM, Giampaolo Rodola' <report at bugs.python.org> wrote:

>
> Giampaolo Rodola' added the comment:
>
> I'm not sure to understand what do you mean by "work tasks".
> Do you need them to have ssl module work with asyncore?
>
> > I've been reading asyncore lately, and feel that it's showing its age.
>
> Absolutely. I'd have some ideas about some asyncore/chat enhancements,
> including writing a poller suitable with epoll and kqueue, but it seems
> there are not enough people who cares enough about asyncore.
>
> __________________________________
> Tracker <report at bugs.python.org>
> <http://bugs.python.org/issue2006>
> __________________________________
>

Added file: http://bugs.python.org/file9357/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/20080205/3258be40/attachment.txt