Re: Challenge: Find potential use cases for non-trivial confinement

[Pierre THIERRY]

Scribit Sam Mason dies 18/05/2006 hora 10:19:
> I've also realised that I don't really understand who pays for the
> resources in the different versions of confinement.  I guess it's time
> for some more reading.

That's always the parent, but not in the same way. In trivial
confinement, the parent gives it's child a capability to some storage
that the parent still can read and write. In the constructor pattern,
the parent gives it's child a capability to some storage it has given up
some rights to, like read or write.

In both cases, the storage belongs to the parent, which can reclaim it
at any moment.

Similarily,
Nowhere man
-- 
address@hidden
OpenPGP 0xD9D50D8A

signature.asc
Description: Digital signature