[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: Marcus Brinkmann
Subject: Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons
Date: Mon, 15 Jan 2007 19:27:53 +0100
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 Emacs/21.4 (i486-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Mon, 15 Jan 2007 12:36:47 -0500,
"Jonathan S. Shapiro" <address@hidden> wrote:
> On Mon, 2007-01-15 at 18:33 +0100, Marcus Brinkmann wrote:
> > So let's separate the issues.  There are two issues:
> > 
> > 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?
> > 
> > 2) Should the algorithm be run in its own address space or not?
> (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.


reply via email to

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