caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Paul Pelzl <pelzlpj@gmail.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] [ANN] capnp-ocaml 2.0.1
Date: Wed, 3 Sep 2014 10:54:00 -0500	[thread overview]
Message-ID: <CANk_VLKxYo5+h0Z4vyx+gjUj0Nzu4h4p2750TpkfZCQ3=-skcA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]

I'm pleased to announce the release of capnp-ocaml 2.0.1. It is available
in OPAM as package "capnp", or from the project website:
https://github.com/pelzlpj/capnp-ocaml

capnp-ocaml is a code generator plugin for the Cap'n Proto serialization
framework. Cap'n Proto's 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.
http://kentonv.github.io/capnproto/

Aside from important bugfixes, this release brings a larger and
better-designed I/O support library for moving messages across various
types of channels. Performance has also been significantly improved; I've
written a blog post about the benchmarking and optimization experience.
http://pelzlpj.github.io/capnp-ocaml/2014/09/02/capnp-ocaml-2.0/

An excerpt from the change log follows.  Enjoy,

Paul


=== Backwards-incompatible changes
* Module `Codecs`: change API to accept the more natural
`BytesMessage.Message.t`
  instead of `Bytes.t list`.
* Module `Codecs`: change API to accept a `compression` specifier, instead
of using
  separate functions and separate types for compressed and uncompressed
streams.
* Module `Message`: `to_storage` now returns a list of (storage, length)
pairs.

=== Other changes
* Module `Codecs`: fix incorrect encoding of framing headers (for example,
  as generated by `serialize`).
* Module `Codecs`: fix infinite loop in `PackedStream` decoding.
* Module `Codecs`: reduce serialized message sizes, by omitting unused
allocation
  regions from the serialized messages.
* Instantiate `BytesMessage = Message.Make(BytesStorage)`, so the user
doesn't always
  need to. (Implementation is furthermore defunctorized for improved
performance.)
* New module `IO`: functions for moving message data through various types
of I/O
  channels.
* Compiler now says something about files it created.
* Corrected compilation errors when using 4.02 `-safe-string`.
* Significant performance improvements across the board.

[-- Attachment #2: Type: text/html, Size: 2442 bytes --]

                 reply	other threads:[~2014-09-03 15:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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_VLKxYo5+h0Z4vyx+gjUj0Nzu4h4p2750TpkfZCQ3=-skcA@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;
as well as URLs for NNTP newsgroup(s).