Leo Sutic wrote:
From: Stephen McConnell [mailto:[EMAIL PROTECTED]
One must be careful in how one positions something as divergent.
Which of the following existing and divergent characteristics within Merlin would you like to eliminate?
None, and that's never been the issue.
The issue is this: Will Merlin keep being divergent in those
characteristics or will there be any incorporation of the charcteristics into the core Avalon code?
Every effort has been made to ensure a good separation of the different facilities within Merlin with the objective of enabling identification, assessment and potential migration of common container-side facilities. There is already a process in place facilitating the migration of the meta-info model out of Merlin and into the core Avalon code. There are other facilities that will progressively establish themselves as candidates. Of particular relevance is a common meta data representation and a common composition model.
In short, are you willing to codify those characteristics as a standard that may not fulfill all your wants but will fulfill all your needs, and then stick to that standard?
Where it makes sense. Take two examples - (a) context, (b) AMTAGS. There was a bunch of work we did (headed up by you) on cleaning up the definition of the Avalon context contract covering context casting and context entry semantics. These semantics are 100% supported within the Merlin platform (context casting, context entry handling, entry alias management, etc.). This is an example of a spec that made sense. The AMTAGS spec. (as it stands today) is an example of a spec that does not make sense because it is simply insufficient. As a consequence AMTAGS are not supported in Merlin (although now with work on a common meta-info layer, chances are that AMTAGS will be revised to something more substantive in which case we may see 100% support in the near future).
One should consider Merlin a work in progress that aims to identify, validate, and establish common facility candidates, and, progressively incorporate standard facilities. Over time I am confident that Merlin will (a) lead the process of delivering standard Avalon containment, while (b) maintaining a healthy and vibrant context for exploration, resolution and delivery of advanced distributed service management.
Part of the process of achieving this objective involves the establishment of a release process - periodic milestone releases of the Merlin platform reflecting its evolution and progressive incorporation of a standard Avalon infrastructure.
Cheers, Steve.
--
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]
