Peter Royal wrote:
One could say that we all strive to perfection, but we never get there... ;-)On Wednesday, November 20, 2002, at 06:03 AM, Berin Loritsch wrote:Multiple containers are not only helpful, but they are absolutely necessary.I think a single container is a goal we should strive towards.
We will never be able to converge on the most generic and useable container
specifications when there is only one to choose from. Using different
approaches that all work with the same components helps us to determine
important criteria such as:
Users don't want to have to pick a container due to separate but overlapping feature sets. We should strive towards a single container that is pluggable to the point of satisfying many needs. I think the current experimentations with multiple containers lets us push things into different directions to see what we may want from that ubercontainer.In fact I do agree that we should strive to have a single container, and the Fortress+Merlin cross-pollination has showed good results. If we have a single container, we can be more united and push forward better and together. This does not mean that we should mandate a single container, not at all, but that this goal has to be in our minds and our hearts.
Java has three JDKs, Micro, Standard and Enterprise. They share much of the language and implementation. ATM we have containers that share the Avalon language, but basically no implementation. Dunno if it makes sense, and it also reminds me of the prior discussions on this, but IMHO it's something worth considering.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
