avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Karasulu <aok...@bellsouth.net>
Subject RE: Clarifying Avalon and Metro
Date Tue, 10 Aug 2004 22:00:01 GMT
On Tue, 2004-08-10 at 15:31, Farr, Aaron wrote:
> Why do I always think of just one more thing to add right after I hit send?
> 
> :)
> 
> One other thought on the Post-Metro Avalon:
> 
> Avalon: The Container|Component|IoC Federation Project
> 
> Another slightly more radical idea on Avalon's role in life after Metro's
> departure is that Avalon could serve as a "federation" project for container
> related development within Apache.  Avalon would provide links and resources
> such as documentation and a "commons" for at least the original Avalon
> projects (Metro and Excalibur) and potentially for related projects
> (Hivemind, Geronimo, etc.).  In this case, Avalon would still host and
> manage Framework and Component development as mentioned before, but would
> also serve as a general gateway to other container, component, or IoC
> development.

+1

That's really groovy Aaron.  I'm glad you decided to repost to your
original email.  We should also keep in mind our friends at jcontainer
as well as the Spring folks.  Avalon should be all about choice.  Let
the users of Cornerstone or the application deployer decide how and what
container to use without having to go in any one particular direction. 
In the end we'll find different environments will require different
containers based on their strengths and weaknesses.  This is the way to
emerge from an oligopoly into a truely healthy competetive environment
where the users are the winners.

Alex



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


Mime
View raw message