At 11:40 28/2/01 -0500, Ted Husted wrote:
>Peter Donald wrote:
>> okay then. What would you propose that Avalon be rechartered as?
>
>If we can move
>
> 1. A repository of general utility code
This really should be split up - it includes things like CascadingThrowable
handling as well as things like JavaBeanized DB component. The first type
of code should definetly go into AUT/library or wherever (And I can move
some of it to a test CVS within minutes of getting permission to do so ;]).
The higher level components (DBPools/other) is where the rub is. Do they
belong in Avalon or in a separate project? Once gump++ is complete then the
distribution method for Avalon will move to it. At which point there will
be two different projects distributing similar components with similar goals.
>then the label "Avalon" could represent the
>union of Phoenix and Cornerstone, the way Tomcat 4.0 represents the
>union of Jasper and Catalina.
Phoenix/Cornerstone will go their own way sometime in the future. They have
more inline with something like Enhydras AppDirector (or whatever it is
called). And are more about writing and hosting servers (mail/web/shell etc).
Besides which there has been some people grumbling that different products
within one project should be avoided ;)
>This would put Avalon back on track with its original charter as a
>"common framework for server applications".
The "framework" part of Avalon is already separated from the rest of it.
Phoenix/Cornerstone/Cocoon (and hopefully Turbine in the future) build on
top of this.
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 |
*-----------------------------------------------------*
