Message62076
| Author |
janssen |
| Recipients |
christian.heimes, giampaolo.rodola, janssen, josiahcarlson |
| Date |
2008年02月05日.18:39:49 |
| SpamBayes Score |
0.0008012105 |
| Marked as misclassified |
No |
| Message-id |
<4b3e516a0802051039t48cbc7d7y8b1bce8644b0a329@mail.gmail.com> |
| In-reply-to |
<1202162433.7.0.199779813194.issue2006@psf.upfronthosting.co.za> |
| Content |
*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@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@bugs.python.org>
> <http://bugs.python.org/issue2006>
> __________________________________
> |
| Files |
| File name |
Uploaded |
|
unnamed
|
janssen,
2008年02月05日.18:39:48
|
|