[cap-talk] Responsibility tracking: fine points: usage cases, log exposure, resource use

Jonathan S. Shapiro shap at eros-os.com
Wed Dec 6 15:29:42 CST 2006


On Wed, 2006-12-06 at 13:16 -0800, Jed at Webstart wrote:
> At 03:06 AM 12/6/2006, Marcus Brinkmann wrote:
> >At Tue, 05 Dec 2006 18:16:44 -0800,
> >Jed at Webstart <donnelley1 at webstart.com> wrote:
> > > 2.  I also believe that when a person initiates almost any program
> > > to work on their behalf then such tracking with revocation should
> > > be used (revoking the "membrane" when the user feels the
> > > program is no longer useful - e.g. after it exits but possibly
> > > before).
> 
> This is also a case where a human action is often involved.
> Even when not (e.g. cron, batch, etc., etc.) I think the
> startup times are such that any overhead from this protocol
> is likely not significant.

As I noted earlier, the overwhelming majority of program executions are
exclusive and private to a single caller. For such programs, there is no
need to undertake the expense of a membrane boundary.


-- 
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100



More information about the cap-talk mailing list