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

Thomas Koch <thomas@koch.ro> Fri, 10 February 2012 14:45 UTC

Return-Path: <thomas@koch.ro>
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 422F421F877F for <imap5@ietfa.amsl.com>; Fri, 10 Feb 2012 06:45:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.696
X-Spam-Level: **
X-Spam-Status: No, score=2.696 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_RO=1.235, HELO_IS_SMALL6=0.556, HOST_EQ_RO=0.904]
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 kNUdNXMXXfth for <imap5@ietfa.amsl.com>; Fri, 10 Feb 2012 06:45:00 -0800 (PST)
Received: from koch.ro (koch.ro [88.198.2.104]) by ietfa.amsl.com (Postfix) with ESMTP id CD26D21F870A for <imap5@ietf.org>; Fri, 10 Feb 2012 06:44:59 -0800 (PST)
Received: from aktaia.intevation.org ([212.95.126.10] helo=t61.localnet) by koch.ro with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <thomas@koch.ro>) id 1RvriZ-0007SW-3v; Fri, 10 Feb 2012 15:44:55 +0100
From: Thomas Koch <thomas@koch.ro>
To: Adrien de Croy <adrien@qbik.com>
Date: Fri, 10 Feb 2012 15:44:50 +0100
User-Agent: KMail/1.13.7 (Linux/3.1.0-1-amd64; KDE/4.6.5; x86_64; ; )
References: <1328732126.32086.140661033971485@webmail.messagingengine.com> <201202090820.28260.thomas@koch.ro> <4F337E61.5040702@qbik.com>
In-Reply-To: <4F337E61.5040702@qbik.com>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201202101544.51364.thomas@koch.ro>
Cc: ietf-imapext@imc.org, imap5@ietf.org, IMAP Protocol Interest List <imap-protocol@u.washington.edu>
Subject: Re: [imap5] Designing a new replacement protocol for IMAP
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: thomas@koch.ro
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: Fri, 10 Feb 2012 14:45:05 -0000

Hi Adrien,

thank you for your insights. I've some more questions inline.

Adrien de Croy:
> * updates.  Would need to poll or use long polling to get real-time
> updates (e.g. notification of incoming mail).
Could Websockets or http://en.wikipedia.org/wiki/Comet_(programming) be of 
help here?

> * complex.  In order to reduce round-trips, you'd have to do many things
> in a single transaction, which would create complexity issues in the
> server and client
I was thinking restful HTTP which by definition is not complex. The question 
is, whether a useful mail fetch protocol could be designed in the constraints 
of rest.
 
> I think it would also be very problematic in the wild, since any http
> intermediary would feel entitled to mess with traffic.  E.g. heuristic
> caching, intercepting proxies etc.
There is an HTTP header to instruct any cache to pipe the request through and 
do no caching. But anybody on any line in any protocol could mess with your 
data.

Have to go now, sorry. :-)

Best regards,

Thomas Koch, http://www.koch.ro