From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <daniel.buenzli@erratique.ch>
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 E6AF77F0BA
	for <caml-list@sympa.inria.fr>; Mon, 29 Aug 2016 23:52:02 +0200 (CEST)
IronPort-PHdr: 9a23:DgM49h94xPC6nP9uRHKM819IXTAuvvDOBiVQ1KB80ugcTK2v8tzYMVDF4r011RmSDNydt64P0reP++C4ACpbsM7H6ChDOLV3FDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3CwN5K6zPF5LIiIzvjqbpqsSVP1kD3WfkKfMqdVPt/F2X7pFXyaJZaY8JgiPTpXVJf+kEjUhJHnm02yjG28Gr4ZR4+D5Rsf9yv+RJUKH9YrhqBecAVGduGykP6cbqrRjOSxeUrjtZCz1O00kAPw+QwBjgX5C5jib7pud8wiDSacH/V7EzHyiv7rdmSQXhoCEDOi8l/WeRgct12vF1uhWk8jB2xY/ZZLa/oPxseqKVKd8TQ2tMWoBbSiFHEIe9R4YVFeMdPP9Fos/2pw1d/lOFGQCwCba3mXdzjXjs0Ph/irx5HA==
Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=daniel.buenzli@erratique.ch; spf=None smtp.mailfrom=daniel.buenzli@erratique.ch; spf=None smtp.helo=postmaster@smtp.webfaction.com
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  daniel.buenzli@erratique.ch) identity=pra;
  client-ip=74.55.86.74;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="daniel.buenzli@erratique.ch";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  daniel.buenzli@erratique.ch) identity=mailfrom;
  client-ip=74.55.86.74;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="daniel.buenzli@erratique.ch";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@smtp.webfaction.com) identity=helo;
  client-ip=74.55.86.74;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="daniel.buenzli@erratique.ch";
  x-sender="postmaster@smtp.webfaction.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BHAQBsrcRXh0pWN0pcHAEBBAEBFwEBBAEBgwoBAQEBAY8fqn+CAYYdAoIVFAEBAQEBAQEBAQEBEgEBAQoLCQkZL4IyBAEVAQSCEQEBBCNWEAsYAgImAgJHEAYbE4glBK4zj0sBAQEBBgEBAQEBIoEDiXiHQiuCLwEEmU+RAgGHdQ6FeoxEg3kegnuBWYZEgUABAQE
X-IPAS-Result: A0BHAQBsrcRXh0pWN0pcHAEBBAEBFwEBBAEBgwoBAQEBAY8fqn+CAYYdAoIVFAEBAQEBAQEBAQEBEgEBAQoLCQkZL4IyBAEVAQSCEQEBBCNWEAsYAgImAgJHEAYbE4glBK4zj0sBAQEBBgEBAQEBIoEDiXiHQiuCLwEEmU+RAgGHdQ6FeoxEg3kegnuBWYZEgUABAQE
X-IronPort-AV: E=Sophos;i="5.30,252,1470693600"; 
   d="scan'208";a="191419428"
Received: from mail6.webfaction.com (HELO smtp.webfaction.com) ([74.55.86.74])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Aug 2016 23:52:01 +0200
Received: from [192.168.5.177] (213-202-69-103.dsl.iskon.hr [213.202.69.103])
	by smtp.webfaction.com (Postfix) with ESMTP id 5BF9C2107F3A;
	Mon, 29 Aug 2016 21:51:58 +0000 (UTC)
Date: Mon, 29 Aug 2016 23:51:55 +0200
From: =?utf-8?Q?Daniel_B=C3=BCnzli?= <daniel.buenzli@erratique.ch>
To: Dario Teixeira <dario.teixeira@nleyten.com>
Cc: Rudi Grinberg <rudi.grinberg@gmail.com>, caml-list
 <caml-list@inria.fr>
Message-ID: <1EA71190C2C049079BE32A69F18ABB9C@erratique.ch>
In-Reply-To: <c99c0fc01ea0bc77cc88eca25701847b@nleyten.com>
References: <f80651ae31d96eac1115bf124d97eac4@nleyten.com>
 <20160829153945.424bhlwpk7pmm6em@rgcaml.localdomain>
 <c99c0fc01ea0bc77cc88eca25701847b@nleyten.com>
X-Mailer: sparrow 1.6.4 (build 1178)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: Re: [Caml-list] Functorising over Cohttp's backends

On Monday 29 August 2016 at 20:42, Dario Teixeira wrote:
> Cohttp is perhaps the poster child for how the Lwt/Async schism
> makes many APIs way more complex than they should be! (Not that
> there's an easy solution to this situation...)

I'd rather say it is the poster child on how not to cope with the lwt/async schism... Don't functorize over IO, provide non-blocking abstractions that can be used with either.

D