Changes by intgr ma...@juffo.org:
--
nosy: +intgr
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2006
___
___
Python-bugs-list mailing list
Facundo Batista added the comment:
Because of Giampaolo suggestion, that is reviewing all these
asyncore/asynchat issues.
--
nosy: +facundobatista
resolution: - duplicate
status: open - closed
__
Tracker [EMAIL PROTECTED]
Giampaolo Rodola' added the comment:
Since this seems to be a duplicate of #1641 I propose to close this issue.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2006
__
___
Bill Janssen added the comment:
Yes, I think we're talking about the same thing, too.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2006
__
___
Python-bugs-list mailing list
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)
Bill Janssen added the comment:
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' [EMAIL PROTECTED] wrote:
Giampaolo Rodola'
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 [EMAIL PROTECTED] wrote:
Yes, that's it exactly. So things without work tasks can still get done.
But timers are the important thing. With timers you
Giampaolo Rodola' added the comment:
Yes, that's it exactly. So things without input FDs can make progress.
But timers are the important thing. With timers you can always
implement work tasks by yourself.
I have the feeling that you're talking about the same thing.
self.call_later(0,
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
Christian Heimes added the comment:
If you are going to spend some time with async event io you may be
interested in my patch #1657. It adds epoll and kqueue.
--
nosy: +tiran
priority: - normal
__
Tracker [EMAIL PROTECTED]
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
Bill Janssen added the comment:
Looks like Giampaolo has already submitted a patch for part of this, in
http://bugs.python.org/issue1641
--
nosy: +giampaolo.rodola, josiahcarlson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2006
New submission from Bill Janssen:
I've been reading asyncore lately, and feel that it's showing its age.
Most loops of this sort (we developed something similar for ILU, about
15 years ago) contain handlers for timers and work tasks, in addition to
input handling. For timers, typically there's
13 matches
Mail list logo
