The other one that comes to my mind off the top of my head (and is also quite old) is Waterken:
https://waterken.sourceforge.net/ Capability people will often distinguish between CapTP-style and "Ken-style" (from Waterken) capabilities. I don't quite remember what the main differences are, though, except that Cap'n Proto is much closer to CapTP. -Kenton On Mon, Dec 26, 2022 at 10:34 PM Jens Alfke <[email protected]> wrote: > > > On Dec 26, 2022, at 3:28 PM, Kenton Varda <[email protected]> wrote: > > I'm not sure what you mean about "(negative) remote capability #". There > are no negative numbers. > > > Oops, I got that from the old E documentation (erights.org.) They used > negative numbers to identify capability IDs that were created on the “other > side” of the connection, i.e. promises. > > (Speaking of which, is there any other good reading material on > capabilities-with-RPC, besides erights.org and your own rpc.capnp?) > > —Jens > > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/CAJouXQ%3DHVp9%2B37VmwS_7W5QdG4kkqQ_SDrMwptUXGfpzvytLCw%40mail.gmail.com.
