Re: Potential use case for opaque space bank: domain factored network stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jonathan S. Shapiro schrieb:
> Second, Jonathan has no objection to having a constructor that
> implements methods
> 
>   createYield()
>   createTranslucentYield()
> 
> with the difference being that the second returns a process capability
> to the invoker. Holding the process capability is sufficient (with a bit
> of helper code that does not need to know anything about the subject
> application) to ensure transitive translucency.

But, if we, as free software enthusiasts, think that any use of
createYield (that is, starting a program you are not allowed to look at)
is bad, why should we include that operation into the interface at all?
And then, why is it unreasonable to consider a different design that
achives the same goal (starting processes, with transparent memory) in a
different and (potentially, at least) easier, simpler to understand way?
- --
- -ness-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFolWsvD/ijq9JWhsRAonRAJsEudgCt9GCUBE4/mZk7WQi0jmbrQCfd//n
PrvjopNWru2v3PBzSS2oH3c=
=VzLb
-----END PGP SIGNATURE-----