[cap-talk] "Same" key

[Dean Tribble]

2 examples:
- Transparent forwarders
- Caps with capabiity bits used for logging data but not behavior difference.

On 2/3/07, Mark S. Miller <markm at cs.jhu.edu> wrote:
> Jonathan S. Shapiro wrote:
> > The problem in this conversation is that we are failing to distinguish
> > correctly between the capability itself and the object that it
> > designates. The EQ relationship is a relationship on capabilities, not
> > objects. In real implementations, two distinct capabilities (i.e.
> > capabilities that are not EQ) may designate the same object because of
> > the way the object server is implemented.
>
> Can you give an example where two not-EQ caps designate the same object?
>
> --
> Text by me above is hereby placed in the public domain
>
>      Cheers,
>      --MarkM
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
>