On Wed, Aug 11, 2010 at 11:55 AM, Matt Hammond <[email protected]>wrote:
> On Wed, 11 Aug 2010 10:18:50 +0100, Sylvain Hellegouarch <[email protected]> > wrote: > > I'm usually not a massive fans of mixins as I find they recreate what is >> the >> core nature of Axon: composability. If I was using my threaded monitor >> above, I'd have something like: >> >> Pipeline(ThreadedMonitor(), >> TestComponent(),PassItOn(),ConsoleEchoer()).run() >> >> >> Where TestComponent wouldn't be a mixing anymore. To me this avoids hiding >> the fact the TestComponent is a timer. Instead it states that it requires >> a >> timer which is a different view. >> > > Its a mix-in because I was lazy and didn't want to branch Axon and modify > the Component class directly :-) > I cant applaud the lazyness-creativity. > > 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. -- - 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.
