From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id A6EBD7FFB2 for ; Fri, 11 Mar 2016 17:15:53 +0100 (CET) IronPort-PHdr: 9a23:mdbQJxKqKEr2b0n/stmcpTZWNBhigK39O0sv0rFitYgUIv3xwZ3uMQTl6Ol3ixeRBMOAu60C27ud4/mocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWM5DIfUi/yKRBybrysXNWC0ILnhqviotX6WEZhunmUWftKNhK4rAHc5IE9oLBJDeIP8CbPuWZCYO9MxGlldhq5lhf44dqsrtY4q3wD89pozcNLUL37cqIkVvQYSW1+ayFmrPHs4CjKVwyJrl4dVH4Vg1IcEg3E6gr5T7/zuy33rfZn1SSGe8bxSOZndy6l6vJFUhbuByAGLAkT92vQloQkgrhSphmmpgc5yYneZ529P/d3OK3HK4BJDVFdV9pcAnQSSri3aJECWq9YZb5V Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=francois.bobot@cea.fr; spf=None smtp.mailfrom=francois.bobot@cea.fr; spf=None smtp.helo=postmaster@cirse-out.extra.cea.fr Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of francois.bobot@cea.fr) identity=pra; client-ip=132.167.192.142; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="francois.bobot@cea.fr"; x-sender="francois.bobot@cea.fr"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of francois.bobot@cea.fr) identity=mailfrom; client-ip=132.167.192.142; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="francois.bobot@cea.fr"; x-sender="francois.bobot@cea.fr"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@cirse-out.extra.cea.fr) identity=helo; client-ip=132.167.192.142; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="francois.bobot@cea.fr"; x-sender="postmaster@cirse-out.extra.cea.fr"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DhAACn7eJWk47Ap4RdvzWBbYYNAoExORMBAQEBAQEBARABAQEBCQsJCSEvgi2CFAEBAQMBIw8BBUEFCwsOCgICBSECAg8CRgYNCAKIGAiuH48iAQEBAQYBAQEBHHyJXoQigxiBOgWXQ5crhVOOcSIDglGBUYs6AQEB X-IPAS-Result: A0DhAACn7eJWk47Ap4RdvzWBbYYNAoExORMBAQEBAQEBARABAQEBCQsJCSEvgi2CFAEBAQMBIw8BBUEFCwsOCgICBSECAg8CRgYNCAKIGAiuH48iAQEBAQYBAQEBHHyJXoQigxiBOgWXQ5crhVOOcSIDglGBUYs6AQEB X-IronPort-AV: E=Sophos;i="5.24,321,1454972400"; d="scan'208";a="168213477" Received: from cirse-out.extra.cea.fr ([132.167.192.142]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Mar 2016 17:15:52 +0100 Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u2BGFqLj007170; Fri, 11 Mar 2016 17:15:52 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F3BCD205BBC; Fri, 11 Mar 2016 17:16:23 +0100 (CET) Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DB800208E03; Fri, 11 Mar 2016 17:16:23 +0100 (CET) Received: from [10.8.32.80] (is222783.intra.cea.fr [10.8.32.80]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u2BGFqYT020600; Fri, 11 Mar 2016 17:15:52 +0100 To: Yaron Minsky References: <56E2C676.3010702@cea.fr> Cc: "caml-list@inria.fr" From: =?UTF-8?Q?Fran=c3=a7ois_Bobot?= Message-ID: <56E2EF38.10603@cea.fr> Date: Fri, 11 Mar 2016 17:15:52 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Icedove/44.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] Question about Lwt/Async 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