avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: [RT] The Ominous Context
Date Thu, 10 Jul 2003 03:43:44 GMT

> Looking at the problem from a 1000 foot view

> I have a very radical solution for identifying common context entries.
> Don't.

So far so good.

>                 -oO Context Declaration and Definition 0o-
> The user of a system has two separate concerns they have to worry about.
>  The first concern has to do with declaration, much like we declare any
> required services that we need for our component.  In fact, I propose we
> follow the same model that we have for services as we do for context
> entries.  That model is that the component declares its requirements,
> and in assembly we identify how those requirements are fulfilled.
> That's right, the second concern which is defining the context entries
> and values belongs to application assembly.
> This solution provides the maximum amount of flexibility for the
> application developer, while ensuring that the system can perform its
> validations and share information accross several components.

Looking from 10,000 feet, what is then the difference between an "object"
residing in Context and one that can be looked up in the ServiceManager??


To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message