Peter Donald wrote:
On Tue, 3 Dec 2002 05:13, Noel J. Bergman wrote:
I saw Pete's comments. I, personally, don't agree with him and I didn'tIf need be I will ;)
see him veto the approach, hence my summary.
By parsable, I mean in accordance with the RFC into the urn:NID:NSS parts.We have spent a lot of time removing the need for parsed lookup keys for ServiceManager/ComponentManager. We have moved to a set of recomended conventions (postfix with "/" then a discriminator) but they are just that - recomendations. They are not enforced or required in many containers.
The NID gets you to the namespace, which should be useful for scalable
container context and with component registration, the NSS is handled by
the namespace and can certainly be a simple key. In other words, the
contract for the NSS is provided by the namespace definition, and can be as
restrictive as desired.
What we currently pass to both Context and CM/SM are unparsed strings. The postfix convention of "/" is a ECM artifact reflecting dynamic resolution and the necessity to parse. Hense a conflict at the framework level and divergent semantics. If the ECM solution had chosen to use a URN structure, then life today would be a lot easier with respect to handling mixed static and dynamic usage.
Something to consider about the URN convention is that it does not impact any existing implementation - you still do things equivalent to map.get( key ). However, if things don't work out, you have a much more structured namespace from within which to potentially resolve request, log information, report etc. Secondly, it well overdue move to getting some rigerouse specification into the Avalon framework.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
