> > The above definition is tightly tied to the nature of the container and
> > the API it supports. Hence what is in the Context in a nested container
> > might not naturally fall into the Context of its parent container.
> yep - and most likely the elements inside a nested containers context are
> possibly defined by services that the parent containre offers.
Seems to me that in the concept of a scalable container, the elements are
likely to be provided by container plug-ins used to make up the profiles.
The core container code might not need any specific involvement with that
facility other than to provide a unified means to access it.
The notion of a "Context" in a profile-based container might be considered a
federation of contexts, not a nesting. If I might use the RFC 2141 example,
the NID identifies a context from the federation, and NSS identifies
something provided by that context.
This is independent of what kinds of data/services are provided by a
context.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
