Who does share my dream?
* A component developed against a set of (one or more) specifications WILL work unmodified in all applications that understand/"complies with" suc specification(s).
* Once components can be "managed" inside and outside applications, it will drive applications in many directions, where containers are only one such branch of development. The better the tools, the faster components can be created, leading to more tool support and so on.
Is it only I who think that Avalon can step up and create this (a.k.a AvalonPlanet)??
I think you will find very few people who will disagree with you. However, the difference between the dream and reality today is quite large, and constant work is needed in this area. But, tightening the spec in Avalon may not be the answer. I, for one, don't want to just use Avalon components. I want to use Jicarilla components, Pico components, Spring components, HiveMind components.....bring them on. No matter what we do in Avalon, there will always be innovation elsewhere. We need to define ways to make the containers more flexible, not tied to a rigid spec.
Shash
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
