> On Wednesday 04 March 2009 00:04:13 Matt Hammond wrote: >> The timeout feature is there, to my mind, because it provide a >> convenient >> way to provide basic timing facilities, very nearly for free (since the >> threading.Event() object it uses to pause has an optional timeout >> argument >> already built in) >> >> In my understanding, there is therefore no difference between >> self.pause() >> for generator based components and threaded components, except from the >> fact that the pause-ing will not happen in a generator based component >> until the next yield statement is reached. > > This second paragraph disagrees with the first.
Apologies - you are correct - a lack of accuracy on my part! More precise 2nd stab: The possible things that may cause a threaded component to re-awaken, when paused, are the same as that for a generator based component (with the addition of the timeout, if specified) A threaded component will be awoken by box related activity (new messages arriving, send messages being collected by a recipient) just as a generator based component would be. Matt -- | Matt Hammond | | [anything you like unless it bounces] 'at' matthammond 'dot' org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
