> > Which you could do as:
> > "urn:NID:NSS"
> > "jini:<jini lookup info>"
> > "role:<role-descriptor>"
> with a single interface exposed to the invoking object.
> Theres already a framework for that - JNDI.
<<grin>> You noticed that, did you. :-) Having written both JNDI clients
and JNDI service providers, it wouldn't bother me to use JNDI as a standard.
It is a bit of overkill, but I could live with it. However, since it can
impact the ability to get small, my thought was to limit the initial
requirement to the composite name lookup aspect, which is fairly trivial to
code (and delegate).
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
