Cap'n Proto and Rust: Type Systems for Sharing
summary
Claims that Cap'n Proto + Rust deliver a zero-copy message format with identical memory and on‑the‑wire representation, a Rust library that enforces lifetimes prevent dangling pointers so readers never outlive buffers, and an RPC runtime built from per‑object tasks and channels that achieves on‑par performance vs C++ in benchmarks. The stack is deployed inside Sandstorm to confine capabilities, avoids encode/decode costs, and the implementation proves practical and secure for real distributed apps.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:02Cap'n Proto and Rust Type Systems for Sharing
- 5:54data and capabilities
- 12:55Cap'n Proto makes data mobile
- 13:24uniformity of representation allows zero-copy mmap()-ready serialization
- 23:46a capability is a reference to an immobile, possibly remote object
- 25:55tasks in Rust cannot cause data races
- 26:51Communicating Sequential Processes
