Re: [imap5] Designing a new replacement protocol for IMAP

Adrien de Croy <adrien@qbik.com> Wed, 15 February 2012 22:51 UTC

Return-Path: <adrien@qbik.com>
X-Original-To: imap5@ietfa.amsl.com
Delivered-To: imap5@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76DAF21E80E8 for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 14:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.128
X-Spam-Level:
X-Spam-Status: No, score=-5.128 tagged_above=-999 required=5 tests=[AWL=-2.529, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id phSj2pq9s3sa for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 14:51:48 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id 56FCC21E80CC for <imap5@ietf.org>; Wed, 15 Feb 2012 14:51:47 -0800 (PST)
Received: From sago.qbik.com (unverified [192.168.0.3]) by SMTP Server [192.168.0.1] (WinGate SMTP Receiver v7.1.0 (Build 3381)) with SMTP id <0018865318@smtp.qbik.com>; Thu, 16 Feb 2012 11:51:46 +1300
Received: From [192.168.0.10] (unverified [192.168.0.10]) by SMTP Server [192.168.0.3] (WinGate SMTP Receiver v7.0.8 (Build 3364)) with SMTP id <0010060123@sago.qbik.com>; Thu, 16 Feb 2012 11:51:37 +1300
Message-ID: <4F3C36F9.2030302@qbik.com>
Date: Thu, 16 Feb 2012 11:51:37 +1300
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120202 Thunderbird/11.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
References: <833EE8EEE88E4ADE5CDDDADB@caldav.corp.apple.com> <4F3835A1.7060804@qbik.com> <B764BD8C8B6047E659EABBE2@caldav.corp.apple.com> <4F397212.1030107@qbik.com> <20120213210805.GB13029@launde.brong.net> <alpine.LSU.2.00.1202151405550.30682@hermes-2.csi.cam.ac.uk> <1329315552.1444.140661036879893@webmail.messagingengine.com> <4F3BBFA4.8010107@isode.com> <1329316981.8310.140661036883625@webmail.messagingengine.com> <66F68487BF0EED4BA7D767E2410F30B3EFF259456A@FRSPX100.fr01.awlatosorigin.net> <20120215211301.GA16253@launde.brong.net> <4F3C2362.2060007@qbik.com> <4F3C3356.6030100@panozzo.it> <3077.1329345730.658893@puncture>
In-Reply-To: <3077.1329345730.658893@puncture>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>
Subject: Re: [imap5] Designing a new replacement protocol for IMAP
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion on drastically slimming-down IMAP." <imap5.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imap5>, <mailto:imap5-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imap5>
List-Post: <mailto:imap5@ietf.org>
List-Help: <mailto:imap5-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2012 22:51:52 -0000

On 16/02/2012 11:42 a.m., Dave Cridland wrote:
> On Wed Feb 15 22:36:06 2012, Giovanni Panozzo wrote:
>> Il 15/02/2012 22:28, Adrien de Croy ha scritto:
>>>
>>> having dealt with support issues relating primarily to HTTP for the 
>>> last
>>> 17 years, I'd STRONGLY recommend against using anything HTTP based. The
>>> number of proxies that break WebDAV makes it problematic alone.
>>>
>>> If some clients need HTTP-based access to some IMAP function, they can
>>> use a gateway.
>>
>> Such a gateway should be a mandatory part of the protocol, or we will 
>> end up on having a lot of servers with the http gateway and many 
>> other servers without it, really bad user experience.
>>
>> Could we think a "skype-like" solution, where the client makes two 
>> attempts:
>>
>> 1) Direct socket connection on a single TCP port
>>  and then, in case of failure
>> 2) https tunnel of the same protocol (thru optional client side proxy).
>>    https is more likely to survive across proxyes than http.
>
> BOSH.

long polling is a hideous hack.  Proxies hate it.

It's basically designing a system to provide a TCP over multiple HTTP 
over TCP connections.  Bloat to the extreme.

I understand the reasons why it exist, due to the model of HTTP, but 
building more things on top of it heading in the wrong direction IMO.

>
> Dave.

-- 
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
WinGate 7 is released! - http://www.wingate.com/getlatest/