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 :-)
The attraction to me if the simplicity of use and the lower overheads
compared to using a threaded component to send timing signalling.
Matt
--
| Matt Hammond
| Research Engineer, BBC R&D, Centre House, London
| http://www.bbc.co.uk/rd/
--
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.
