From: Trevor Smith <trevorsummerssmith@gmail.com>
To: Malcolm Matalka <mmatalka@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Protobuf and OCaml
Date: Thu, 26 Feb 2015 14:54:35 +0000 [thread overview]
Message-ID: <CAG-KTt8sKbByimaqFU+fc9-teM4VjVekM-L7LH+BTzQiLQPk3A@mail.gmail.com> (raw)
In-Reply-To: <CAKziXDV42J3R3wFriXZL-jyDKP2VYBQDB9eTuSunpJTnScDD6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Thanks for your input Kenneth and Malcolm. Helpful.
Trevor
On Wed Feb 25 2015 at 1:35:57 PM Malcolm Matalka <mmatalka@gmail.com> wrote:
> At the moment I think whitequark's is probably the simplest, easiest,
> and most well tested. Ocaml-protobuf will be implemented in terms of his
> once I get sufficient time and motivation. Ocaml-protobuf provides a
> monadic interface which I prefer and whitequark's does a lot of the heavy
> lifting for you.
> Den 25 feb 2015 18:00 skrev "Trevor Smith" <trevorsummerssmith@gmail.com>:
>
> Hello,
>>
>> Is anyone out there using OCaml with Protobufs? If so, what library/tools
>> are you using, and how do you like the setup? Also, are you using Protobufs
>> in a production setting?
>>
>> I found online but have not used any of the below myself:
>>
>> 1) piqi - http://piqi.org/
>> 2) obitz - https://github.com/orbitz/ocaml-protobuf
>> 3) whitequark's protobufs - https://github.com/orbitz/ocaml-protobuf
>>
>> Curious to hear your experiences. Thank you.
>>
>> Trevor
>>
>
[-- Attachment #2: Type: text/html, Size: 1914 bytes --]
next prev parent reply other threads:[~2015-02-26 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 16:58 Trevor Smith
2015-02-25 17:32 ` Kenneth Adam Miller
2015-02-25 18:35 ` Malcolm Matalka
2015-02-26 14:54 ` Trevor Smith [this message]
2015-02-26 15:07 ` Koen De Keyser
2015-02-26 15:15 ` Kenneth Adam Miller
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=CAG-KTt8sKbByimaqFU+fc9-teM4VjVekM-L7LH+BTzQiLQPk3A@mail.gmail.com \
--to=trevorsummerssmith@gmail.com \
--cc=caml-list@inria.fr \
--cc=mmatalka@gmail.com \
/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