Leo Simons wrote:
Putting this to use?
--------------------
So, should we now add Executor support to Merlin, along with thread monitoring coupled with dynamic component reloading on thread disruption? If so, where do we hook it in, and how?
IMO, this stuff should be an optional extension only and it should not disrupt existing code or make it too complex. In order to do that, some merlin refactoring might be required :D
It's in beta - refactoring is fair game! Seriously though - 2.1 was a lot more dynamic and extendible at the runtime level than 3.0. But 3.0 is a lot better the 2.1 with respect to model separation (and related model management). I want to see 2.1 dynamics coming back in - but consistent with the model/runtime separation.
Things in mind:
1. pluggable lifestyles 2. pluggable lifecycle strategies 3. plugable facilities (e.g. JMX) 4. events and listeners
Cheers, Steve.
p.s. BTW ... good post!
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
