[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:10:26 -0500 |
On Mon, 2007-01-15 at 18:48 +0100, Neal H. Walfield wrote:
> > (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.
>
> ... and likely should not have. Yet, if the yield is running our of
> client provided transparent storage, the client effectively has access
> to the database. So, don't you want these types of services to run as
> daemons?
Absolutely not. I want to be able to safely polyinstantiate them, which
is why I need client-provided storage to be opaque.
--
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100
- Re: Translucent storage: design, pros, and cons, (continued)
- Re: Translucent storage: design, pros, and cons, Tom Bachmann, 2007/01/12
- Program instantiation (was: Re: Translucent storage: design, pros, and cons, Marcus Brinkmann, 2007/01/12
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Jonathan S. Shapiro, 2007/01/14
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Marcus Brinkmann, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Jonathan S. Shapiro, 2007/01/15
- constructor daemon vs. constructor library, Neal H. Walfield, 2007/01/15
- Re: constructor daemon vs. constructor library, Jonathan S. Shapiro, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Marcus Brinkmann, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Jonathan S. Shapiro, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Neal H. Walfield, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons,
Jonathan S. Shapiro <=
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Neal H. Walfield, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Jonathan S. Shapiro, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Neal H. Walfield, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Pierre THIERRY, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Marcus Brinkmann, 2007/01/15
- Re: Program instantiation (was: Re: Translucent storage: design, pros, and cons, Jonathan S. Shapiro, 2007/01/15
- Capability simulation, Jonathan S. Shapiro, 2007/01/11
- Handing off... (was: Re: Translucent storage: design, pros, and cons), olafBuddenhagen, 2007/01/12
- Layering in EROS/Coyotos, Jonathan S. Shapiro, 2007/01/11
- Re: Translucent storage: design, pros, and cons, Jonathan S. Shapiro, 2007/01/11