From: Ivan Gotovchits <ivg@ieee.org>
To: Romain Bardou <romain.bardou@inria.fr>
Cc: Tom Ridge <tom.j.ridge+caml@googlemail.com>,
caml-list <caml-list@inria.fr>,
Benedikt Grundmann <bgrundmann@janestreet.com>
Subject: Re: [Caml-list] Thread behaviour
Date: Tue, 01 Oct 2013 07:32:59 +0400 [thread overview]
Message-ID: <87ioxhvf6c.fsf@golf.niidar.ru> (raw)
In-Reply-To: <52493343.7020509@inria.fr> (Romain Bardou's message of "Mon, 30 Sep 2013 10:16:03 +0200")
Romain Bardou <romain.bardou@inria.fr> writes:
> It happens I implemented a library to handle messaging between
> possibly-distributed OCaml processes myself. Well, for now one can only
> send one message and receive one message: the goal is to be able to run
> a function 'a -> 'b in another process, given marshaling functions for
> 'a and 'b and exceptions. I do plan to add the possibility of sending
> more "intermediate" messages (I need it). It works on Linux and Windows.
>
> I did not do any official release yet, but you can have a look here:
>
> https://github.com/cryptosense/procord
>
And it happens that I implemented yet another such library. It is in a
heavy use and battle tested in a commercial product, but it is not
yet released, and may have some hidden bugs. Also it doesn't work on
Windows (it uses fork, pipes and AF_UNIX sockets).
The main idea behind the library is to play the same role for Lwt, as
Async_parallel plays for Async. Forking with lwt (or any other async
framework) is not an easy stuff, but it is doable. The second goal I
pursued is to make its interface as simple as possible. Task can be
created as easy, as «Parallel.run (print_endline "Hello, world")».
I hope I will release it at the beginning of the next year.
--
(__)
(oo)
/------\/
/ | ||
* /\---/\
~~ ~~
...."Have you mooed today?"...
next prev parent reply other threads:[~2013-10-01 3:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 10:10 Tom Ridge
2013-09-27 10:22 ` Simon Cruanes
2013-09-27 10:27 ` Romain Bardou
2013-09-27 10:51 ` Benedikt Grundmann
2013-09-28 19:09 ` Tom Ridge
2013-09-29 7:54 ` Tom Ridge
2013-09-29 12:37 ` Yaron Minsky
2013-09-29 16:25 ` Tom Ridge
2013-09-29 16:46 ` Chet Murthy
2013-09-29 17:18 ` Tom Ridge
2013-09-29 17:47 ` Chet Murthy
2013-09-30 8:24 ` Romain Bardou
2013-10-07 14:57 ` Goswin von Brederlow
2013-09-30 8:16 ` Romain Bardou
2013-10-01 3:32 ` Ivan Gotovchits [this message]
2013-10-07 14:49 ` Goswin von Brederlow
2013-09-30 9:18 ` Xavier Leroy
2013-09-30 15:12 ` Tom Ridge
2013-09-30 16:01 ` Török Edwin
2013-09-30 16:56 ` Gabriel Kerneis
2013-09-30 18:18 ` Alain Frisch
2013-10-01 5:01 ` Pierre Chambart
2013-10-01 7:21 ` Gabriel Kerneis
2013-10-02 10:37 ` Wojciech Meyer
2013-10-02 11:52 ` Francois Berenger
2013-10-02 11:58 ` Wojciech Meyer
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=87ioxhvf6c.fsf@golf.niidar.ru \
--to=ivg@ieee.org \
--cc=bgrundmann@janestreet.com \
--cc=caml-list@inria.fr \
--cc=romain.bardou@inria.fr \
--cc=tom.j.ridge+caml@googlemail.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