Re: [SUMMARY] Context Concensus

Paul Hammant wrote:
> Darrell.
> 
> Non-committers opinions noted.
> 
>> Now, nothing stops Phoenix from having a BlockContext implementation 
>> that just does:     return this;
> 
> Except that change the usage pattern.
> 
>> when asked for that key. And nothing *prevents* a component from 
>> directly casting, except that the component is then <i>tightly tied to 
>> Phoenix</i> because this is <i>not defined in the Framework</i> 
>> contracts.
> 
> Sorry to be pedantic.  No that component is tied to BlockContext which 
> is part of Phoenix, but ships in a client api jar. There has been 
> discussion before about how trivial to implement for a container this 
> is.  We even voted it should be the case for Merlin. Nobody made the 
> change though.  Too much respoect for Stephen, his resistance to that 
> resultion, and not enogh sub-project karma.

Please show me the thread of that vote and the resolution, I would like 
to remember how it went.


-- 
Nicola Ken Barozzi                   [email protected]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------