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: Thu, 26 Feb 2015 10:15:37 -0500	[thread overview]
Message-ID: <CAK7rcp-r3dwUqyTtd4NpneTuOJbvU=Or9EjbMsSCx2wUDGYpow@mail.gmail.com> (raw)
In-Reply-To: <CAP+7bo06huN+9JqyiSJr+gLGkLmRC=oYYEVF7qJ2MFfEtOYE_g@mail.gmail.com>

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

Well put Koen.

The other thing that's interesting is that with the build chain being piqi
-> proto files, you can add support for languages to automatically support
your data schema other than what the original protocol buffers project
provides for. So, originally pb started with python, java, and C/++. Now it
supports Google's go and all kinds of other languages.

On Thu, Feb 26, 2015 at 10:07 AM, Koen De Keyser <koen.dekeyser@gmail.com>
wrote:

> I've worked with Piqi, converting a project that was using custom
> serialization to Protobuf. This was a fairly pleasant experience: the main
> developer was very responsive and the code base for the code generator is
> sufficiently clean that it made adding custom functionality quite easy.
>
> The main reason I went with Piqi is the code generation functionality: one
> of the main reasons to adopt something like Protobuf is the possibility of
> generating code in a multitude of languages (e.g. Python for scripting /
> testing purposes) from a single definition file (the proto file in this
> case). Any change there is automatically picked up by the build process in
> all of the languages, so your code stays in sync across languages. This is
> not the case if the definition of the struct is in Ocaml itself.
>
> Koen De Keyser
>
> On Wed, Feb 25, 2015 at 5:58 PM, 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: 3090 bytes --]

      reply	other threads:[~2015-02-26 15:15 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
2015-02-26 15:07 ` Koen De Keyser
2015-02-26 15:15   ` Kenneth Adam Miller [this message]

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-r3dwUqyTtd4NpneTuOJbvU=Or9EjbMsSCx2wUDGYpow@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).