Split Capabilities: Making Capabilities Scale

[Mark S. Miller]

At 04:42 AM 7/1/00 , Jonathan S. Shapiro wrote:
> > Besides, we can't really use that approach [the directory of capabilities
> > approach] in e-speak because of the
> > additional latency.  The two step process you describe doubles the
>latency.
> > That's because in e-speak the holder of the strong capability is a
>service,
> > not an object.
>
>In KeyKOS/EROS it's also a service, though it helps that the systems are not
>distributed.

What do you guys mean by "service" vs "object"?


         Cheers,
         --MarkM