From: "Jérémie Dimino" <jeremie@dimino.org>
To: guillaume.yziquel@citycable.ch
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Recursion on React.events.
Date: Fri, 11 Dec 2009 13:16:38 +0100 [thread overview]
Message-ID: <1260533798.5029.97.camel@aurora> (raw)
In-Reply-To: <4B21750F.9060707@citycable.ch>
Le jeudi 10 décembre 2009 à 23:24 +0100, Guillaume Yziquel a écrit :
> Yes. It's also here where I worry about a few things concerning Lwt:
>
> In Lwt, you have a monadic way to do context switches for multithreading
> withing a single real thread. So if you use Lwt inside the update cycle,
> you could well jump out of the update cycle with a Lwt context switch.
> As long as you do not encounter a Lwt construct within definition of
> signals and events, you can be pretty sure that the update cycle will go
> through to its end without using Lwt inside an event/signal. But at the
> same time, it seems that the monadic way Lwt is built avoids us such
> problems. But I may be mistaken.
It is possible to use Lwt inside an update cycle. It is not a problem to
switch context in an update cycle as long as you respect React's rules.
> So the compatibility of Lwt and React seems to me a worthwile question
> if one wants to use OCaml for high availability, reactive, parallel
> computations. And in this context, making E/S.switch easy to use would
> quite important...
Thanks to React being lowlevel, the two libraries are compatible out of
the box.
Jérémie
next prev parent reply other threads:[~2009-12-11 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 2:40 Guillaume Yziquel
2009-12-09 3:22 ` Guillaume Yziquel
2009-12-09 4:25 ` Daniel Bünzli
2009-12-09 18:47 ` Guillaume Yziquel
2009-12-10 8:39 ` Daniel Bünzli
2009-12-09 7:53 ` Daniel Bünzli
2009-12-09 11:23 ` [Caml-list] " Richard Jones
2009-12-09 18:01 ` Guillaume Yziquel
2009-12-10 3:38 ` Daniel Bünzli
2009-12-10 22:24 ` Guillaume Yziquel
2009-12-11 12:16 ` Jérémie Dimino [this message]
2009-12-09 18:24 ` Guillaume Yziquel
2009-12-10 8:24 ` Daniel Bünzli
2009-12-10 21:41 ` Guillaume Yziquel
2009-12-11 1:22 ` Daniel Bünzli
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=1260533798.5029.97.camel@aurora \
--to=jeremie@dimino.org \
--cc=caml-list@inria.fr \
--cc=guillaume.yziquel@citycable.ch \
/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