At 10:00 28/2/01 -0500, Ted Husted wrote:
>Peter Donald wrote:>> Avalon is;
>> 1. A repository of general utility code
>> 2. A repository of patterns and framework code
>> 3. A set of general utility code based on (2)
>> 4. A micro kernel for running services
>> 5. A set of services that are orientated towards server environments
>And in the spirit of cooperation ;-) I'd suggest that since Avalon has
>so much on its plate already, why not try and offload (1) to the
>Commons, and concentrate more fully on (2) through (5)+.
Possible - we want to move out the general low level utility code
(cascading exceptions/enums/collection utils/cli tools) into another
project. In the latest proposal it has been moved to aut (Apache utility
toolkit) that we were going to propoose to you guys once it is clearer how
to separate these things. In the future 4-5 will hopefully move to another
project and 3 will be integrated with library. Which leaves but (2) in
avalon. Thus Avalon has ceased to be a place for server-side components and
would then be just an alternate component model similar to JavaBeans but
different ;)
Changing a projects charter from server-side component repository to
component model so that another project can become a server-side component
repository is not something that I think I would like to do ;)
>Even with the reorganization, I think the perception is going to be that
>Avalon is a framework product that also offers up some general utility
>code, the same way Struts and Turbine do.
easy enough to rebrand ;)
>The difference between Avalon and the Commons is that Avalon is trying
>to put the pieces together, and the Commons is really offering pieces,
>only pieces, and nothing but pieces. BYOP - bring your own puzzle ;-)
Yes and no. Phoenix and cornerstone try to put the things together but the
other parts are separate.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
