Stephen,
your point is taken that all operations that are not a lookup of a
constant value based on a key (such as getHomeDirectory)
can be seen as a peer service.
First, everything can be seen as a peer service. We don't really
need the Configurable interface. Instead, one could lookup a
configurator service:
interface Configurator {
Configuration getConfiguration ();
}
and use the returned Configuration. The container would ensure you
got the correct config.
However, while it reduces the set of classes one has to deal with
("everything is a service") there are practical issues with this.
Peter D. mentioned a few of them here:
http://marc.theaimsgroup.com/?l=avalon-dev&m=103809692826408&w=2
and I believe he's right.
My analysis would be that the real problem *is* the Context interface.
Specifically, that it is a total mess. What is it for? Constant value lookup?
Container specific services only? Container provided services in general?
If anything, this is something that has to be solved before we go on.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
