avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bennett, Timothy (JIS/Applications)" <TimothyBenn...@jis.nashville.org>
Subject RE: Regarding The Avalon Framework
Date Thu, 08 Jul 2004 21:08:56 GMT
> -----Original Message-----
> From: Farr, Aaron [mailto:Aaron.Farr@am.sony.com] 
> Sent: Thursday, July 08, 2004 3:06 PM
> To: avalon-dev
> Cc: 'Leo Simons'
> Subject: Regarding The Avalon Framework
> 
> I am not trying to halt further development of the framework 
> or limit Merlin's potential.  In fact, I believe this will 
> help development of Avalon-compliant systems by providing the 
> needed documentation.  It will also clear up confusion about 
> what it means to be Avalon compliant.  

...And here is the thing that some of us can't seem to grasp... What does it
mean to be Avalon-compliant?  It is NOT merely compliant with the framework
API.  The MAJOR issue IMO is that if I (or any Avalon user) writes a Avalon
component, then I expect it drop seemlessly into ANY *Avalon-compliant*
container and it work straight-up without any modifications.  For that to
happen, Avalon-compliancy must encompass more than just framework
compatibility.  It must include standards for meta and such.

I'm not interested in documenting only the Framework and dubbing that what
it means to be Avalon-compliant because we still haven't addressed that big
picture problem that Avalon components are not compliant across Avalon
containers.  So, until we are prepared to roll out a *real* set of Avalon
standards and TCK that defines compliancy beyond merely the framework, I see
no need to confuse the issue of compliancy by pre-maturely pushing forward
just the framework in order to satisfy legacy containers which will
undoubtably not be Avalon-compliant when we complete our standards and TCK.

The way I see it is that there will be:

Framework-compliant

and

Avalon-compliant

The reason we have a new single platform focus, a new web site, and
Excalibur/Fortress promoted as a TLP is so that we can make
Avalon-compliancy an eventual reality, with Avalon-compliancy meaning
component drop-in execution across Avalon-compliant containers.

Regards,
Timothy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org


Mime
View raw message