avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Single Avalon Implementation yes/no/why/how ( Re: CVS organization )
Date Wed, 20 Nov 2002 14:51:11 GMT
Federico Barbieri wrote:
> 
> >Paul Hammant wrote:
> >  
> >
> >>(Vote) -1
> >>
> (strong opinion) -0.99
> 
> two reasons:
> first there is been tension and flames, if you force everyone into the 
> same room you'll get more. Let the dust settle first.
> second IMHO avalon scope is wide enough to justify more than one 
> implementation (not many but more than one).
> I may want to *focus* on performances, scalability, user friendlness, 
> resource usage etc.
> 
Ok, as I tried to express, I agree on having different implementations
because of scalability and performance, but not on features.

But perhaps it's really better to see the development of the current
implementations grow nad have a look then at what we have.

Carsten

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


Mime
View raw message