From: Francois Berenger <berenger@riken.jp>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Cc: batteries-discuss@lists.forge.ocamlcore.org,
OCaml Beginners List <ocaml_beginners@yahoogroups.com>
Subject: Re: [Caml-list] library/framework needed for distributed programming in OCaml
Date: Thu, 12 Jul 2012 17:46:06 +0900 [thread overview]
Message-ID: <4FFE8ECE.4050007@riken.jp> (raw)
In-Reply-To: <20120711132142.42636h39ppnk3vsm.lealanko@webmail.helsinki.fi>
Hello,
For the moment, the best answer I got privately in my mailbox
is to combine Janestreet's bin_prot and async libraries
or Martin Jambon's biniou with Lwt.
I kind of like what I read on async and bin_prot.
On 07/11/2012 07:21 PM, Lauri Alanko wrote:
> Hi.
>
> I also had need of such a library when I started working on a
> distributed programming project, but as I couldn't find anything that
> fulfilled my requirements, I wrote my own.
>
> The library is Lwt-based, and provides pretty straightforward remotely
> callable procedures:
>
> type ('a, 'r) handle
> val ($) : ('a, 'r) handle -> 'a -> 'r Lwt.t
> val publish : ('a -> 'r Lwt.t) -> ('a, 'r) handle
>
> The library is designed to work in a firewalled environment: firewalled
> nodes can join the distributed network by connecting to any accessible
> host of that network with an open listener. All messages between nodes
> are routed through the network.
>
> type connection
> val connect :
> ?host:string -> ?port:int -> unit -> connection Lwt.t
> val listen :
> ?port:int -> unit -> unit Lwt.t
>
> Initial values are obtained with "roots". A root (usually a handle, or a
> record or first-class module containing handles) is keyed to a string,
> and once set by a node, it can be discovered by any node in the network:
>
> val get_root : string -> 'a Lwt.t
> val set_root : string -> 'a -> unit Lwt.t
>
> This is the only unsafe part of the interface: the getter and setter
> _must_ agree on the type of the root or all hell breaks loose.
>
> I haven't published the library yet, since I have wanted to feel free to
> modify it as required by my application, but if you are interested, and
> cannot find a more mature solution, I'd be happy to provide it for your
> inspection.
If you publish your code somewhere (github is really nice), I would
be very happy to have a look at it.
Thanks a lot,
F.
prev parent reply other threads:[~2012-07-12 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 6:40 Francois Berenger
2012-07-11 10:21 ` Lauri Alanko
2012-07-12 8:46 ` Francois Berenger [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=4FFE8ECE.4050007@riken.jp \
--to=berenger@riken.jp \
--cc=batteries-discuss@lists.forge.ocamlcore.org \
--cc=caml-list@inria.fr \
--cc=ocaml_beginners@yahoogroups.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