> -----Original Message-----
> From: Mark S. Miller [mailto:markm@caplet.com]
> Sent: Sunday, July 09, 2000 10:05 AM
> To: Jonathan S. Shapiro
> Cc: Karp, Alan; e-lang@eros-os.org
> Subject: Re: Split Capabilities: Making Capabilities Scale
>
>
> 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
>
In e-speak, service == resource. E-speak deals with things that have repository entries. It doesn't care if the thing is active (service) or passive (resource); it does the exact same thing for both. I believe that you use "object" in the sense of a bit of code that does things, i.e., a service. I've been using "object" in the sdnse of a thing that you want to control access to.