On Wed, 30 Jan 2002 09:11, [EMAIL PROTECTED] wrote:
> Is there a fundamental clash of philosophies between the two that is yet
> to be resolved? Is it resolvable?
The main difference is that you should not be able to vote on things you are
not a developer on. Other than that it is largely window dressing differences.
> My understanding so far is that Avalon is a standard framework for
> server-side applications, providing a set of common components to assist
> in that framework.
>
> And that Commons is a set of common components for use in any framework.
Well you understanding is wrong ;) But quite a few people have made an active
effort to make you believe that so it is forgiveable. The majority of Avalons
components are framework agnostic or have framework agostic base classes.
Go back to the initial discussions about commons and you will see that its
current structure was advocated by an AValon developer and that is based on
the structure of the Avalon component repository ;)
> Avalon predates Commons, but has a less bazaar like atmosphere(?).
I wouldn't say that. Most things are go there. We have had different
implementations of things at different times (4 pool architectures
simultaneously were present) but the only difference is that in the end we
tend to work together more and merge bits together.
--
Cheers,
Pete
----------------------------------------
Whatever you do will be insignificant,
but it is very important that you do it.
--Gandhi
----------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
