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

Adrien de Croy <adrien@qbik.com> Wed, 15 February 2012 23:18 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 1D7CB21E804B for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 15:18:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.917
X-Spam-Level:
X-Spam-Status: No, score=-4.917 tagged_above=-999 required=5 tests=[AWL=-2.319, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 HOkaXn3OFl2o for <imap5@ietfa.amsl.com>; Wed, 15 Feb 2012 15:18:18 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id F156221E8032 for <imap5@ietf.org>; Wed, 15 Feb 2012 15:18:17 -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 <0018865373@smtp.qbik.com>; Thu, 16 Feb 2012 12:18:16 +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 <0010060151@sago.qbik.com>; Thu, 16 Feb 2012 12:18:02 +1300
Message-ID: <4F3C3D2A.2050609@qbik.com>
Date: Thu, 16 Feb 2012 12:18:02 +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.awatosorigin.net> <20120215211301.GA16253@launde.brong.net> <4F3C2362.2060007@qbik.com> <4F3C3356.6030100@panozzo.it> <3077.1329345730.658893@puncture> <4F3C36F9.2030302@qbik.com> <3077.1329346432.849825@puncture>
In-Reply-To: <3077.1329346432.849825@puncture>
Content-Type: multipart/alternative; boundary="------------060201020207080607050301"
Cc: "IMAP5 list." <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 23:18:23 -0000

thanks for the pointer on BOSH.

<OT>

Some of the claims they make are patently false however.  Especially in 
http://xmpp.org/extensions/xep-0124.html Sec 4.

"Therefore, if over time the traffic to and from the client is balanced, 
bandwidth consumption will be about the same as if a standard TCP 
connection were being used"

this completely ignores the overhead of the HTTP request and HTTP 
response, which can be very large.  A protocol layered over BOSH which 
makes lots of small transmissions will have its bandwidth consumption 
greatly increased.  IME most transactions have an http overhead > 1KB.  
There are minimum requirements for headers which must be included in 
order to be valid HTTP.  So telnet over BOSH would increase bandwidth 
consumption by 500 times.

It's quite amazing this statement remains in that document.

</OT>


On 16/02/2012 11:53 a.m., Dave Cridland wrote:
> On Wed Feb 15 22:51:37 2012, Adrien de Croy wrote:
>> 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.
>
> There are two options if you want to live in the web world - BOSH or 
> WebSockets.
>
> WebSocket support is *far* from universal, and BOSH works - and works 
> very well with proxies, despite whatever personal feelings they may have.
>
> Dave.

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