-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bas Wijnen wrote: >> I'd like to encourage everyone to consider this. It sounds like a viable >> compromise > > What exactly is "this"? >
The proposal by jonathan: > There are opaque and translucent banks. The difference is that > the opaque bank will not issue a given page more than once. A > translucent bank will, which is how the user gains access to > the content. > > An opaque bank can be a child of a translucent bank (or the > other way around). > > There is a permission restriction on banks that prohibits formation > of opaque sub-banks. If this bit is set, only translucent sub-banks > can be allocated (this preserves recursive translucency). > > If an object is allocated from an opaque bank, it is marked (within > the allocator) as opaque, and no parent bank will disclose it. - -- - -ness- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEcsvqvD/ijq9JWhsRAveFAKCBFEembVJwNwHbO0IkD0laC4bxOgCdE5Ua G9hPNgAxSBSXRGo29MnzBDA= =5jq2 -----END PGP SIGNATURE----- _______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
