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 10:22:59 -0500	[thread overview]
Message-ID: <CACLX4jSpStB1F9XUa6zM+Ak2Axn6qr2GeOB7XSjuzys_QigbVA@mail.gmail.com> (raw)
In-Reply-To: <56E2C676.3010702@cea.fr>

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.

So, with some overhead, yeah, I think you could do it.

y

On Fri, Mar 11, 2016 at 8:21 AM, François Bobot <francois.bobot@cea.fr> wrote:
> On 07/03/2016 18:03, Yaron Minsky wrote:
>>
>> - Async is more portable than it once was.  There's now Core_kernel,
>>    Async_kernel and Async_rpc_kernel, which allows us to do things like
>>    run Async applications in the browser.  I would think Windows
>>    support would be pretty doable by someone who understands that world
>>    well.
>>
>>    That said, the chain of dependencies brought in by Async is still
>>    quite big.  This is something that could perhaps be improved, either
>>    with better dead code analysis in OCaml, or some tweaks to
>>    Async_kernel and Core_kernel themselves.
>>
>
> Is it possible and simple to write a Lwt_Async_rpc based on Async_rpc_kernel
> which would expose Lwt.t functions that dispatch or serve Async_rpc rpcs?
>
> Thanks,
>
> --
> François
>
>
>
> --
> 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-03-11 15:23 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 [this message]
2016-03-11 16:15         ` François Bobot
2016-03-11 17:49           ` Yaron Minsky
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=CACLX4jSpStB1F9XUa6zM+Ak2Axn6qr2GeOB7XSjuzys_QigbVA@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).