caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@janestreet.com>
To: "François Bobot" <francois.bobot@cea.fr>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Question about Lwt/Async
Date: Fri, 11 Mar 2016 12:49:11 -0500	[thread overview]
Message-ID: <CACLX4jTnrDkLnqcgLJ8zKaUS6_9ei3PxMm=7V1sT2ETDcaedeg@mail.gmail.com> (raw)
In-Reply-To: <56E2EF38.10603@cea.fr>

Well, Async_rpc_kernel is tied to the Deferred type, so it's not so
general as to abstract over which IO monad is being used.  So I'm
afraid it doesn't give you a nice way of interoperating with Async
programs.

That said, we're hopefully going to do a rewrite of the protocol in
the next few months.  It's not crazy that we could try to make some of
the low level protocol work shareable, at least.

y

On Fri, Mar 11, 2016 at 11:15 AM, François Bobot <francois.bobot@cea.fr> wrote:
> On 11/03/2016 16:22, Yaron Minsky wrote:
>>
>> Not easily at present, I think. Obviously. if you run two runtimes in
>> two threads, you can do it, but it's ugly.  If you had
>> lwt-on-async-runtime available, as was discussed in the thread, then
>> you could do it, but you'd need some extra overhead to create matching
>> pairs of Lwt.t's and Deferred.t's, since those two types would not be
>> equal.
>>
>
> Sorry I don't know if have been clear that I was thinking to make two ocaml
> process communicate together one using Async and the other Lwt. The use case
> for example, is to write a job server with Async and to make a web interface
> for it using ocsigen (Lwt); so the webserver (Lwt) would connect to the job
> server (Async) using the rpc protocol defined by Async_rpc_kernel.
>
>
>> So, with some overhead, yeah, I think you could do it.
>
>
> Does you answer is applicable to this use case?
>
> Thank you already for this answer.
>
> Best,
>
> --
> François

  reply	other threads:[~2016-03-11 17:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07  1:38 Yotam Barnoy
2016-03-07  7:16 ` Malcolm Matalka
2016-03-07  9:08   ` Simon Cruanes
2016-03-07 14:06     ` Yotam Barnoy
2016-03-07 14:25       ` Ashish Agarwal
2016-03-07 14:55         ` rudi.grinberg
2016-03-07 14:59           ` Ivan Gotovchits
2016-03-07 15:05             ` Ivan Gotovchits
2016-03-08  6:55         ` Milan Stanojević
2016-03-08 10:54           ` Jeremie Dimino
2016-03-07 15:16 ` Jesper Louis Andersen
2016-03-07 17:03   ` Yaron Minsky
2016-03-07 18:16     ` Malcolm Matalka
2016-03-07 18:41       ` Yaron Minsky
2016-03-07 20:06         ` Malcolm Matalka
2016-03-07 21:54           ` Yotam Barnoy
2016-03-08  6:56             ` Malcolm Matalka
2016-03-08  7:46               ` Adrien Nader
2016-03-08 11:04               ` Jeremie Dimino
2016-03-08 12:47                 ` Yaron Minsky
2016-03-08 13:03                   ` Jeremie Dimino
2016-03-09  7:35                     ` Malcolm Matalka
2016-03-09 10:23                       ` Gerd Stolpmann
2016-03-09 14:37                         ` Malcolm Matalka
2016-03-09 17:27                           ` Gerd Stolpmann
2016-03-08  9:41     ` Francois Berenger
2016-03-11 13:21     ` François Bobot
2016-03-11 15:22       ` Yaron Minsky
2016-03-11 16:15         ` François Bobot
2016-03-11 17:49           ` Yaron Minsky [this message]
2016-03-08  5:59 ` Milan Stanojević

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='CACLX4jTnrDkLnqcgLJ8zKaUS6_9ei3PxMm=7V1sT2ETDcaedeg@mail.gmail.com' \
    --to=yminsky@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=francois.bobot@cea.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).