[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Program instantiation (was: Re: Translucent storage: design, pros, a

From: Jonathan S. Shapiro
Subject: Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons
Date: Mon, 15 Jan 2007 14:12:05 -0500

On Mon, 2007-01-15 at 19:27 +0100, Marcus Brinkmann wrote:
> > > 1) Should a linking (interpreter selection etc) algorithm be provided
> > >    along with the program files or should it exist in the ambient
> > >    space of the operating system?
> > 
> > (1) is infeasible in a system where the instantiating party does not
> > have access to the capabilities that the program will require. One
> > purpose of the constructor mechanism is to allow (e.g.) an instantiated
> > password agent to have access to the password database when I do not.
> As I was discussing my system structure proposal (or in other words,
> the Hurd, not Coyotos), this objection doesn't apply.

I think it does, but only in the sense that a good system structuring
proposal should clearly identify the strengths and weaknesses of the
policies it selects.

This applies to my proposal too, of course.
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100

reply via email to

[Prev in Thread] Current Thread [Next in Thread]