[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] ReactiveML and Mirage

  • To: manu delab <manu.delab@xxxxxxxxx>, mirageos-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Drup <drupyog+caml@xxxxxxxx>
  • Date: Mon, 20 Apr 2015 00:28:24 +0200
  • Delivery-date: Sun, 19 Apr 2015 22:28:36 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type; b=b+L1Xw0kuStS4mr8aLI9mqyVYxxKrlihhQ2CP6eVrTBH90dEfIQeyYPMY3ci/4RTytdsWyOZBXpy 88q0HCqKACf2lkp6vY9pO0N+x9R6cdKc8kEV2jy6XpaECMgTtP1c
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

Le 19/04/2015 23:58, manu delab a écrit :

I noticed that the Ocisgen folks were looking at Reactive Synchronous languages
Just for the record, that is not exactly true. We don't use Reactive ML, mostly React and some custom made things. The project mentioned in this job offer is about reactivity in the context of client-server communication and multiple agents, not one computer. Reactive ML doesn't help you for that, and solutions remains to be invented, hence the project.

That doesn't diminish the interest of Reactive ML on Mirage, just clarifying things a bit. ;)

I was wondering if anybody had an opinion about what advantages (if any), this approach to concurrency could bring to Mirage (as opposed to using something like Lwt)
For instance, RML has handy constructs for task communication and synchronization.

Since RML compiles to OCaml code, it should be possible to experiment with it in the context of Mirage applications (once the dependencies on Unix are removed).

Here are a few examples from the RML distribution, running in the browser via js_of_ocaml:



MirageOS-devel mailing list

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.