[cap-talk] revoking capabilities yetmaintain structure/functionality, garbage collection

Karp, Alan H alan.karp at hp.com
Fri Jan 13 12:32:17 EST 2006


John Carlson wrote:
> 
> I don't think I am communicating.  Say you have a highly 
> linked set of 
> web documents.
> You share a read/write capability on the set of documents with a 
> person.  Later, you
> decide that you want to revoke that person's right to access the 
> documents.   We have
> revocation for a single object, but what do you do if the object is 
> really a bunch of links,
> all with YURLs?  

That's what membranes are for.  Revoke the capability to the membrane
and all capabilities passed through it are revoked.  See
http://www.eros-os.org/pipermail/e-lang/2003-January/008434.html.

________________________
Alan Karp
Principal Scientist
Virus Safe Computing Initiative
Hewlett-Packard Laboratories
1501 Page Mill Road
Palo Alto, CA 94304
(650) 857-3967, fax (650) 857-7029
https://ecardfile.com/id/Alan_Karp
http://www.hpl.hp.com/personal/Alan_Karp
  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Karp, Alan H.vcf
Type: text/x-vcard
Size: 423 bytes
Desc: Karp, Alan H.vcf
Url : http://eros.cs.jhu.edu/pipermail/cap-talk/attachments/20060113/a14cabb9/KarpAlanH.vcf


More information about the cap-talk mailing list