caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Protobuf and OCaml
Date: Wed, 25 Feb 2015 12:32:39 -0500	[thread overview]
Message-ID: <CAK7rcp-msFncdKj_gcpr0Ka6yDoujtWyVia7x2iFrxoHeFQARQ@mail.gmail.com> (raw)
In-Reply-To: <CAG-KTt-VDGQyqaBXH8yS028QaGZDSHNRgqa+dd1MbzY2JHM4DA@mail.gmail.com>

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

Yeah, I use ocaml and protobuf. I use Piqi a lot, and it works fine. It's
easy to use piqi. You write your data types in the piqi language, and then
derive your .proto files from it using the piqic compiler. You can then do
the normal things with protobuf compilers to generate whatever language
bindings you want.

Yes, I have protobuf in two scenarios (one for binary analysis, another for
custom binary instrumentation) at my work, and I find it works nicely.

On Wed, Feb 25, 2015 at 11:58 AM, Trevor Smith <trevorsummerssmith@gmail.com
> wrote:

> 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: 1774 bytes --]

  reply	other threads:[~2015-02-25 17:32 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 [this message]
2015-02-25 18:35 ` Malcolm Matalka
2015-02-26 14:54   ` Trevor Smith
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=CAK7rcp-msFncdKj_gcpr0Ka6yDoujtWyVia7x2iFrxoHeFQARQ@mail.gmail.com \
    --to=kennethadammiller@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).