Peter Royal wrote:
On Thursday, July 31, 2003, at 08:13 AM, Stephen McConnell wrote:
Carsten Ziegeler wrote:
So, if I understand this correctly, the idea is to start a new version from scratch (of course not really from scratch we already have the framework interfaces)?
Basically, I like the idea because by this it's possible to have a real community development effort with avoiding the one-man shows >> etc.
Carsten, I agree with you.
As I mentioned to Berin - I'm not about to start over - simply because there its just plain boring and a recepie for discontent. Been there, done that, want to continue on the really challenging stuff. Think about distributed containers, federated management, adaptive component security. This is the future - a future where it challenges the best or our abilities - a future where we are not going over old ground attempting to convince each other that direction X is the best direction.
Stephen, why was Merlin started, as opposed to branching/working within the existing Phoenix codebase?
Merlin actually started out in life as a little component runner that handled the problem of developing components under Phoenix. Phoenix was a remains a really heavy-weight tool when all you want to do is a runtime test. The idea was to to create an ant task that would take a target component and deploy it. In doing so it had to figure out depednecies and other stuff without forcing the developer to write a bunch of assembly files package the thing in a ar file, and lauch Phoenix. That's was Merlin 1.0.
Merlin 2 emergaged as was a result of working with Peter Donald on the containerkit package. That package was all about formalizing the component/container contract. Peter's work was largely focussed on the Phoenix requirements wheras my own requirements were more dynamic and included embedded scenarios - a subject not handled by any container solution available in Avalon at the time. Over time, Merlin has developed to incorporate many end-user requirements relating to practical and simple service management.
My opinion is that you wanted a codebase where you had control over it.
No - not at all.
And you have been positioning Merlin to be in a place to ascend to be the primary Avalon container.
Actually - if you go back to previuse posts I have consistently stated that I would like to see Merlin as a project that facilitates experimentation, and that through validation in the real word, there may perhaps be sub-system that can be proposed as common solutions. Merlin is just a project that can contributes to the bigger avalon picture in interesting ways.
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
