On Wed, Aug 11, 2010 at 12:16 PM, Matt Hammond <[email protected]>wrote:
> The attraction to me if the simplicity of use and the lower overheads >>> compared to using a threaded component to send timing signalling. >>> >> > With the understanding of blocking the whole Python process (hence the >> scheduler) by not using a thread for the timer. >> > > It doesn't block the scheduler. It uses the python Timer class, which uses > a thread. When the timer times-out, the component is re-awoken, if paused. > > > Damn, that'll teach in reading the code more properly. I assumed it was a time.sleep(...). Sorry for that. -- - Sylvain http://www.defuze.org http://twitter.com/lawouach -- You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en.
