> What do you guys mean by "service" vs "object"?
In EROS/KeyKOS I do not think that there is a distinction, except in some fine semantic sense. I think of the "object" as the thing named by a capability. It exhibits behavior in response to invocations. I think of the service as the program that implements the behavior of the object. The distinction is mostly useful because a single service can implement mulitple objects (and multiple object types).
I am picking nits. For the purposes of this discussion it suffices to say that a directory in EROS is an object.