Stephen McConnell wrote, On 17/07/2003 3.37:
...
We cannot have Melin be divergent. We need one spec to drive the user
expectations.
One must be careful in how one positions something as divergent.
Which of the following existing and divergent characteristics within Merlin would you like to eliminate?
Bullshit, Stephen. You are just generating negative energy, sit down a minute and think of it. It's *not* about how to remove "divergent" things, it's about how to *integrate* them.
Berin said:
"Before I can be OK with that, we need to ensure that all user components are defined consistently across all containers. The meta API separated out is a step in that direction. We need to be assured that the same component used in Merlin will continue to function in Fortress, and vice versa. "
To make the same component run in two different containers, you have three options:
1 - make the featureful one degrade - which is out of question 2 - make components require a specific container - you know it's not best 3 - make the other container upgrade to the new features, or even better make the two integrate into one that has the best of both
Merlin has cool features? Cool! When will it become *the* Avalon container? What is missing for it to become so? What does Fortress have that cannot and/or will not put into Merlin?
-- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) ---------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]