At 05:47 PM 6/14/2002 +0200, you wrote:
>Hi everyone,
>
>I would like to have your vote on this design constraint on Avalon 5:
>
> all possible efforts should be done to avoid avalon forking
Avalon has already been forked. There is a whole bunch of stuff in there
that was added in for Cocoon that is not used anywhere else. A5 will unify
the model or else it wont occur at all. A4 may not be perfect but it is
definelty good enough for me. The problems with it are due to misuse of
features and lack of unified metadata or container utilities.
Metadata support is underway and hopefuly will ease that pain. Container
utilities are also on the way and hopefully that will encourage people to
not misuse features (by not natively supporting them).
>So, what do you think?
It is a good idea. However if anyone was to try and force usage patterns
that result from a specific container - especially when those usage
patterns could be considered problematic then I think it wont work.
I have looked at all the containers and believe I know where we can
continue to work together but there are somethings there will need to be
compromises from all. However when I hear predictions of Doom and
ultimatims I find myself thinking A4 is going to be about for a long time
yet ;)
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
