From: Paul Pelzl <pelzlpj@gmail.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] [ANN] capnp-ocaml 1.0.0
Date: Mon, 7 Jul 2014 08:46:58 -0500 [thread overview]
Message-ID: <CANk_VLKq3bpH9UGU0OkzhpgdhfwKOQ3JNcjZ6-Wk5TNeNavfDw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
I'm pleased to announce the first release of capnp-ocaml:
https://github.com/pelzlpj/capnp-ocaml
Cap'n Proto is a multi-language serialization framework which uses code
generation techniques in a manner similar to Protocol Buffers. Its
distinguishing feature is that there is no explicit parsing/serialization
step: the on-the-wire message format is also designed to serve as an
efficient in-memory data structure representation.
The capnp-ocaml code generator plugin emits pure OCaml code which is
functorized over the underlying message format. At present, a 'bytes'-based
message format is provided for ease of use with file and socket I/O. In the
future, a Bigarray message format could be easily provided; this would lend
itself to a straightforward method for sending and receiving messages via
an mmap'd shared memory region.
Q: Why would I want to use this over sexplib/bin-prot?
A: These projects provide superior language-level integration, but
capnp-ocaml is a better choice if you care about language portability.
Q: Why would I want to use this over Protocol Buffers?
A: Cap'n Proto has the clear advantage of first-class sum types, which are
mapped to OCaml variants in a straightforward fashion. You also find
yourself intrigued by the potential for better performance and
zero-overhead shared-memory message passing.
capnp-ocaml is available on OPAM as package "capnp".
Paul
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next reply other threads:[~2014-07-07 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 13:46 Paul Pelzl [this message]
2014-07-07 15:10 ` Peter Zotov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANk_VLKq3bpH9UGU0OkzhpgdhfwKOQ3JNcjZ6-Wk5TNeNavfDw@mail.gmail.com \
--to=pelzlpj@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox