Re: Object Capability model for IoT
"Karp, Alan H" <[email protected]>
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <8AD823089998C849A832D86972E69CD5418A2DF2@G4W3222.americas.hpqcorp.net> |
David Barbour wrote: è Consider: when object information is encoded directly in the string, you can 'drop' that information by the simple (and entirely local) act of dropping the string. However, when object information is encoded in an extrinsic table, however, the information sticks around long after you drop the capability, and so you need a distributed garbage collection process to eventually remove the information from the system. Fundamentally, it is these 'mapping tables' that are GC'd, not 'objects'. Maybe I don’t understand your use case, but I don’t see why you can’t (lazily) clean up the table to remove entries for dropped objects. ________________________ Alan Karp Principal Scientist Enterprise Services, Office of the CTO Hewlett-Packard Company 1501 Page Mill Road Palo Alto, CA 94304 1 (650) 386-4568 http://www.hpl.hp.com/personal/Alan_Karp _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk