On Feb 4, 2015, at 14:56, Matthew Taylor <[email protected]> wrote: > Another task that progresses us towards this common goal is an > independent serialization format. Scott has been working on > implementing the Cap'n Proto serialization protocol ...
Cap'n Proto handles structured, strongly typed data, is very fast (particularly for in-memory communication), and has bindings for a variety of languages: https://capnproto.org/ https://capnproto.org/encoding.html https://capnproto.org/faq.html https://capnproto.org/language.html https://capnproto.org/otherlang.html Like Protocol Buffers and Thrift (but unlike JSON or MessagePack), Cap’n Proto messages are strongly-typed and not self-describing. You must define your message structure in a special language, then invoke the Cap’n Proto compiler (capnp compile) to generate source code to manipulate that message type in your desired language. -- https://capnproto.org/language.html I generally prefer stringly-typed, self-describing serialization formats (eg, YAML), because they facilitate inspection, mocking, etc. However, I'd be OK with any format that can be translated in and out of a human-readable representation. -r -- http://www.cfcl.com/rdm Rich Morin [email protected] http://www.cfcl.com/rdm/resume San Bruno, CA, USA +1 650-873-7841 Software system design, development, and documentation
