From: rixed@happyleptic.org
To: Jon Ludlam <jon@recoil.org>
Cc: Yaron Minsky <yminsky@janestreet.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] RPC for OCaml?
Date: Wed, 18 May 2016 16:34:09 +0200 [thread overview]
Message-ID: <20160518143409.GC10232@pim.happyleptic.org> (raw)
In-Reply-To: <20160518141715.GA6168@humongous>
-[ Wed, May 18, 2016 at 03:17:15PM +0100, Jon Ludlam ]----
> github.com/mirage/ocaml-rpc
A very quick look at this a while ago gave me the impression that this was only
a serializer. If so, then I must say I've always considered only two families
of serializers:
- legacy ones (json, protobuf...) for real situations
- standard lib Marshal for tests
But indeed there might be room for an ocaml-centric serializer with
best-in-town type checking but that does not crash programs compiled with
different versions of the compiler :-)
next prev parent reply other threads:[~2016-05-18 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 13:43 rixed
2016-05-18 13:52 ` Yaron Minsky
2016-05-18 14:17 ` Jon Ludlam
2016-05-18 14:34 ` rixed [this message]
2016-05-18 14:26 ` rixed
2016-05-18 19:01 ` Yaron Minsky
2016-05-18 17:42 ` Chet Murthy
2016-05-19 9:29 ` rixed
2016-06-26 5:56 ` David MENTRÉ
2016-05-18 19:59 Maxime Ransan (BLOOMBERG/ 731 LEX)
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=20160518143409.GC10232@pim.happyleptic.org \
--to=rixed@happyleptic.org \
--cc=caml-list@inria.fr \
--cc=jon@recoil.org \
--cc=yminsky@janestreet.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;
as well as URLs for NNTP newsgroup(s).