[cap-talk] Persistence as a cap value
James A. Donald
jamesd at echeque.com
Sun Mar 16 07:01:31 EDT 2008
James A. Donald
>> A capability is a transmissible permission. If a program receives the
>> permission as part of its install time configuration, this is a
>> software pattern resembling an ACL.
Pierre THIERRY wrote:
> Not at all, because nothing says you have only one such endowment for a
> program. You can setup multiple constructors with very different
> authorities, for the same program, and each user can do that
> independently. Even each *object* that has been given the authority to
> do this could create such a setup independently. That's very unlike an
> ACL pattern to me.
Indeed so, but to me it is very unlike a pattern that user could manage.
More information about the cap-talk
mailing list