On Wed, 2005-10-19 at 14:21 +0200, Bas Wijnen wrote: > What Marcus described was that A wants a capability from a server, and gets it > via the cap server. Then we have: > > Server->CapServer->A > > Then A copies its capability to B via the capability server. Then it is > Server->CapServer-->A > `->B
Bas: In order to make sure that your mental picture of this protocol is precise, could you please resend it using my expanded notation, where every transfer is explicitly state? > I note that the capability server as a library approach isn't being discussed > at the moment. Is there something wrong with it? As a transitional implementation for application bringup it's fine, but I suspect that it is insecure. Can you describe it under a new subject line, or point me at an existing description in the email archives? shap _______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
