Re: Single Avalon Implementation yes/no/why/how ( Re: CVS organization)

[Federico Barbieri]

Carsten Ziegeler 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.

And what can I do, if I want to combine to open source projects,
the first one using container implementation A and the second
one container implementation B? Hmmm.

The idea is they should both been Afalon framework compatible and so in an idel world component should be container independent. Whenever this is not going to happend it will be time to work together.
My vision is that AF is the Java language specification and each container is a different vm implementation.
Component should be 100% pure avalon.

fede

Carsten

--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>