Peter Donald wrote:
> On Wed, 28 Aug 2002 07:28, Peter Donald wrote:
>
>>Im not so sure it is to use "context" as the namespace -esepcially given
>>that these attributes are scoped. The way these three are named in what I
>>am doing is the following
>>
>>component:home.dir=
>>component:work.dir=
>>component:common.classloader=
>>partition:home.dir=
>>partition:work.dir=
>>partition:common.classloader=
>>application:home.dir=
>>application:work.dir=
>>application:common.classloader=
>
> On second thoughts, "*:common.classloader" would clash with the ideas in some
> containers. Blech - maybe just X:classloader instead.
I think that common.classloader is better, since it says that the
classloader can be shared, as Leo says.
Also it makes naming consistent:
X:detail.what
If we use component, partition and application specifiers, though, we
should formalize them in framework.
I think that the concept is generic enough to be there.
example:
component - we know what
partition - space shared by sets of components
application - assembly of components
Hmmm...
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
