Author janssen
Recipients janssen
Date 2008-02-04.05:52:00
SpamBayes Score 0.00108659
Marked as misclassified No
Message-id <>
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 a list of tasks and
times, often with a repeat period.  A system timer is set to the time of
the next task to fire, and the select() loop is exited when it fires. 
The loop handler then looks down the list of timer tasks, and executes
those ready to run.  Similarly, most loops of this sort include a list
of work tasks, and a policy for executing them, such as "take one task
from the front of the list and run it, then do the select".  This allows
background tasks to get run that don't have associated input or output fds.
Date User Action Args
2008-02-04 05:52:08janssensetspambayes_score: 0.00108659 -> 0.00108659
recipients: + janssen
2008-02-04 05:52:07janssensetspambayes_score: 0.00108659 -> 0.00108659
messageid: <>
2008-02-04 05:52:01janssenlinkissue2006 messages
2008-02-04 05:52:00janssencreate