Jeremie, other than having some different back-ends available (e.g., glib
main loop), how different are the approaches to backend management between
Async and Lwt?

y

On Tue, Mar 8, 2016 at 6:04 AM, Jeremie Dimino <jdimino@janestreet.com>
wrote:

> On Tue, Mar 8, 2016 at 6:56 AM, Malcolm Matalka <mmatalka@gmail.com>
> wrote:
>
>> Yotam Barnoy <yotambarnoy@gmail.com> writes:
>>
>> > Out of curiosity, what polling mechanism is available on the lwt side?
>>
>> I believe Lwt supports multiple event loops underneath, including libuv
>> to get whatever polling the OS supports.
>
>
> ​Yes, by default Lwt has a backend using Unix.select, and a libev one if
>  available at compile time (`opam install conf-libev`)
> ​. At runtime Lwt will use the Unix.select backend by default, except if
> it was configured to choose the libev one (the default on Linux) [1].
>
> There is also a backend using the glib main loop, for GTK applications
>
>  [1]
> https://github.com/ocsigen/lwt/blob/master/_oasis#L88
>
> --
> Jeremie
>