aboutsummaryrefslogtreecommitdiff
path: root/libraries/capnproto/README
diff options
context:
space:
mode:
authorAndre Barboza <bmg.andre@gmail.com>2017-01-09 21:10:13 +0700
committerDavid Spencer <idlemoor@slackbuilds.org>2017-01-09 20:18:25 +0000
commitd7b75355bc2764894859e9bfec983b930e69b020 (patch)
tree7c2e5905fae0949396cf1d1841668285bbc561aa /libraries/capnproto/README
parentab838742fcbc6684cbacca077ccd27b614ce39ec (diff)
libraries/capnproto: Added (Cap'n Proto serialization/RPC system).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'libraries/capnproto/README')
-rw-r--r--libraries/capnproto/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/libraries/capnproto/README b/libraries/capnproto/README
new file mode 100644
index 0000000000000..6f7064c9334ba
--- /dev/null
+++ b/libraries/capnproto/README
@@ -0,0 +1,11 @@
+Cap'n Proto is an insanely fast data interchange format and
+capability-based RPC system. Think JSON, except binary. Or think
+Protocol Buffers, except faster. In fact, in benchmarks, Cap'n Proto
+is INFINITY TIMES faster than Protocol Buffers.
+
+This benchmark is, of course, unfair. It is only measuring the time
+to encode and decode a message in memory. Cap'n Proto gets a perfect
+score because there is no encoding/decoding step. The Cap'n Proto
+encoding is appropriate both as a data interchange format and an
+in-memory representation, so once your structure is built, you can
+simply write the bytes straight out to disk!