On Wednesday 10 March 2004 18:26, Leo Sutic wrote:

> >     6. If so, what should it consist of?
>
> The framework spec should consist of... Avalon/Framework.
>
> There are holes in the framework API spec as it is now - for example,
> poolable components (ECM) versus all-components-are-singletons
> (Phoenix).
> Those should be plugged to enable component compatibility.

Just curious, 
You don;t consider, for instance, 

 * Lookup semantics, such as a Selectors and hierarchical naming, 
 * Context entries, and
 * Meta-info formats and 'locations'

as "semantic holes" in the current Framework?


Cheers
Niclas

-- 
+---------//-------------------+
|   http://www.bali.ac         |
|  http://niclas.hedhman.org   |
+------//----------------------+

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

Reply via email to