Peter Donald wrote:

> At 05:36 PM 7/1/2002 +0200, you wrote:
>
>> Keeping *both* sides (container writer / container user) simple is
>> another goal... Too much complexity in the container -> crap container
>> -> implosion.
>>
>> I agree that the above argument may sound like a non-argument ("we can't
>> do that because, well, we can't do such things") and I have no proof
>> that
>> three containers with common core set of libraries is simpler, it is
>> just what I as an Avalon developer suspect.
>
>
> It is technically feasible to have one container and even relatively 
> simple if you layer the architecture properly.


However, what Pete is failing to point out is that the proper 
architecture will require that you *never* reference context related 
entries or context interfaces (such as BlockContext and related entries  
- which independently of Pete's approach is a common practice across the 
Avalon community). In addition, Pete failed to point out that you must 
have implicit knowledge as a developer of the ideas about constraints on 
a component that have never been documented.  Unfortunately, if you fail 
to read all of the thousands of messages on this list - they you are 
totally hosed and its your fault because your suffering from a low IQ 
and bad advise. 

However, a common framework is technically possible - we just have to 
work around the above problems.

Cheers, Steve,

(who tends to respect constraints based on what's documented in a formal 
specs.)



>
>
> 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]>
>

-- 

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net




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

Reply via email to