I’m pleased to announce the release of capnp-rpc 0.2, an OCaml implementation of the RPC specification. This release adds support for persistence, encryption and access control (via tokens in sturdy refs):
https://discuss.ocaml.org/t/ann-capnp-rpc-0-2-persistence-encryption-and-access-control/826 There is an extended tutorial at https://github.com/mirage/capnp-rpc/blob/master/README.md Note: I'm not completely happy about the handling of sturdy refs in the API. In particular, they appear in messages as data, and reading them gives a URI. This has to be turned back into a sturdy ref object manually (with `Vat.import my_vat sr`). I think that some changes to the schema language and protocol are needed to support this properly: 1. The schema language should define SturdyRef<Interface> as a built-in type. Schema compilers can then generated typed bindings for this. Currently, they appear as untyped AnyPointer fields. 2. The CapDescriptor enum should have a new "sturdy" variant (similar to thirdPartyHosted, but holding a SturdyRef), so that sturdy refs are treated the same as other references. In particular, the protocol handler needs to turn these SturdyRef data structures into sturdy-ref objects (with connect methods) within to the receiving vat. -- 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 capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
