Cap'n Proto is a type system for distributed systems.
With Cap'n Proto, you describe your data and interfaces in a schema file, like this:
@0x986b3393db1396c9;
struct Point {
x @0 :Float32;
y @1 :Float32;
}
interface PointTracker {
addPoint @0 (p :Point) -> (totalPoints :UInt64);
}
You can then use the capnp tool to generate code in a variety of programming languages. The generated code lets you produce and consume values of the types you've defined in your schema.
In Rust, the generated code for the example above includes
a point::Reader<'a>
struct with get_x()
and get_y()
methods,
and a point::Builder<'a>
struct with set_x()
and set_y()
methods.
The lifetime variable 'a
in these generated struct types
is a formal reminder that they contain borrowed references to
the raw buffers of bytes that make up the underlying Cap'n Proto messages.
Those underlying buffers are never actually parsed into
separate data structures -- Cap'n Proto's wire format also serves as its in-memory format.
That is, there is no encode or decode step!
It's in this sense that Cap'n Proto is
"infinity times faster"
than alternatives like Protocol Buffers.
The generated code also includes
a point_tracker::Server
trait with an add_point()
method,
and a point_tracker::Client
struct with an add_point_request()
method.
The former can be implemented to create a network-accessible object,
and the latter can be used to invoke a possibly-remote instance of a PointTracker
.
- capnproto-rust (the repo you're looking at right now): Runtime library for dealing with Cap'n Proto messages.
- capnpc-rust: The Rust code generator plugin, including
support for hooking into a
build.rs
file in acargo
build. - capnp-futures: Support for asynchronous reading and writing of Cap'n Proto messages.
- capnp-rpc-rust: Object-capability remote procedure call system.
addressbook serialization, RPC
- Sandstorm's raw API example app and collections app
- leaf
- fractalide
- combustion-engine
- Orphans
- Dynamic reflection
- Pointer constants and defaults