caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Ludlam <jon@recoil.org>
To: Yaron Minsky <yminsky@janestreet.com>
Cc: rixed@happyleptic.org, "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] RPC for OCaml?
Date: Wed, 18 May 2016 15:17:15 +0100	[thread overview]
Message-ID: <20160518141715.GA6168@humongous> (raw)
In-Reply-To: <CACLX4jTkpB+htX2oe7WZ=wt9Rfut=gDrAjCa-PAnkEXyZovR+w@mail.gmail.com>

Mirage has a simple RPC generator that fits the same hole as Async-RPC,
which we use quite heavily in XenServer. It's camlp4 dependent right now,
which I'm keen to fix in the near future.

    github.com/mirage/ocaml-rpc 

I'll certainly be casting a careful eye over the Async-RPC versioning
support as our current versioning story is somewhat primitive.

Jon

On Wed, May 18, 2016 at 09:52:13AM -0400, Yaron Minsky wrote:
> Async-RPC is perhaps worth looking at, though I agree it doesn't give
> you much of what you want --- certainly, we don't to RPC over HTTP, we
> do it over bog-standard TCP, and the protocol is very much
> OCaml-specific, being based on bin-io.  That said, it might be useful
> to look at for inspiration, in particular for how versioning is
> handled in Versioned_rpc.  We do also have some kerberos support in
> there as well, though I'm not sure that's in the open source release.
> 
> On Wed, May 18, 2016 at 9:43 AM,  <rixed@happyleptic.org> wrote:
> > Hello.
> >
> > I'm thinking about implementing a library for doing RPC with OCaml, with large
> > scale environments in mind (à la Stubby but with better type checking of
> > course). I'm wondering what are the related libs I should make myself familiar
> > with before starting. I've seen a few interesting things for serialization
> > (piqi come to mind), some interesting event engines (LWT, Core), some protocol
> > implementations suitable for transport but no HTTP2, nothing to interface with
> > monitoring subsystems or TSDBs, nothing related to load balancing, routing,
> > DDoS detection, etc, some crypto, an interesting TLS implementation from
> > MirageOs, no OAuth or similar.
> >
> > What other related projects should I look at?
> >
> > Also, if anyone would be interested in contributing ideas, experience or code
> > please let me know.
> >
> >
> > --
> > Caml-list mailing list.  Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
> 
> -- 
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2016-05-18 14:20 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 [this message]
2016-05-18 14:34     ` rixed
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=20160518141715.GA6168@humongous \
    --to=jon@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=rixed@happyleptic.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).