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

Bron Gondwana <brong@fastmail.fm> Thu, 16 February 2012 22:31 UTC

Return-Path: <brong@fastmail.fm>
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 E23BF21E8093 for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 14:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.564
X-Spam-Level:
X-Spam-Status: No, score=-3.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 dZVMJ0vhmXvH for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 14:31:06 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id E8BE021E8092 for <imap5@ietf.org>; Thu, 16 Feb 2012 14:31:05 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 967C820CD3 for <imap5@ietf.org>; Thu, 16 Feb 2012 17:31:05 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Thu, 16 Feb 2012 17:31:05 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=mesmtp; bh=fYJrpLukDe3695QUqXNsDPK3 jjo=; b=QU8eEaszSFc0jnii8d0qbzO1alk10iWRe2sBF/xDAioEb1OidZqm0BZ5 +SUTFnZyzTqomrHepFQb/xtVq876fnOec7rBmGz2ZRrP2WHjIXM//fQy+chA75oJ K1GT+TER7NtD8eNFaAWVNrwd2avINhmJU23dz5L9taq7d8YMzX8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=fYJrpLukDe3695QUqXNsDPK3jjo=; b=n/IB98Td6+ZOM73k8FBl37VcHB0T 03nXEIYFUzjq8mw8xGntvqCF0dFweNFt1XHDuHFLwCTl+kl6zp1GF0V2o36CqE5h cGgYsepMgI8s7y6bZpL3JlT+JPnJLrTPlAfYM0vhQnDfCeMtHA6TSWoBeZllSI0L 5VQfdzlZS/2CmXg=
X-Sasl-enc: Cd29po1tKKQUKQATBkpRuhekA9L60RRgPiCxo2p4SrH/ 1329431465
Received: from localhost (99.249.9.46.customer.cdi.no [46.9.249.99]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4F0954824CB; Thu, 16 Feb 2012 17:31:05 -0500 (EST)
Received: by localhost (Postfix, from userid 1000) id 115F72260C3; Thu, 16 Feb 2012 23:31:04 +0100 (CET)
Date: Thu, 16 Feb 2012 23:31:04 +0100
From: Bron Gondwana <brong@fastmail.fm>
To: Adrien de Croy <adrien@qbik.com>
Message-ID: <20120216223104.GC24183@launde.brong.net>
References: <1329316981.8310.140661036883625@webmail.messagingengine.com> <66F68487BF0EED4BA7D767E2410F30B3EFF259456A@FRSPX100.fr01.awl.atosorigin.net> <20120215211301.GA16253@launde.brong.net> <alpine.LSU.2.00.1202161126410.31357@hermes-2.csi.cam.ac.uk> <1329396103.8954.140661037328961@webmail.messagingengine.com> <alpine.LSU.2.00.1202161305220.30682@hermes-2.csi.cam.ac.uk> <20120216145745.GB21339@launde.brong.net> <alpine.LSU.2.00.1202161520460.31357@hermes-2.csi.cam.ac.uk> <20120216191827.GA22862@launde.brong.net> <4F3D6E87.9060006@qbik.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4F3D6E87.9060006@qbik.com>
Organization: brong.net
User-Agent: Mutt/1.5.21 (2010-09-15)
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: Thu, 16 Feb 2012 22:31:11 -0000

On Fri, Feb 17, 2012 at 10:00:55AM +1300, Adrien de Croy wrote:
> one thing - what do you mean by "one big pool".

Similar to quotaroot - "messageroot".  We're going to do it
with users and the conversations database.  For now they're
actually locked to users, but it doesn't handled thousands
of shared folders well, because they would all shared one
central DB.  So one 'root' per user which shares a single
highestmodseq and uidvalidity counter.

In particularly, we could then enforce every single folder
having a different UIDVALIDITY, so we could use a single 64
bit value to uniquely identify message/folder.  It would even
allow multiple consecutive messages in the same folder to
compress into a range.

This will allow supporting shared folders quite nicely by
rooting each one in itself as a standalone folder, no shared
state.

That's the idea, anyway.

Bron.