Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP

Adrien de Croy <adrien@qbik.com> Tue, 21 February 2012 05:29 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 433B621F84F8 for <imap5@ietfa.amsl.com>; Mon, 20 Feb 2012 21:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.555
X-Spam-Level:
X-Spam-Status: No, score=-3.555 tagged_above=-999 required=5 tests=[AWL=-0.956, 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 hKTDdnNr16RX for <imap5@ietfa.amsl.com>; Mon, 20 Feb 2012 21:29:24 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id 4546A21F84EC for <imap5@ietf.org>; Mon, 20 Feb 2012 21:29:22 -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 3385)) with SMTP id <0018874531@smtp.qbik.com>; Tue, 21 Feb 2012 18:29:20 +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 <0010062855@sago.qbik.com>; Tue, 21 Feb 2012 18:29:11 +1300
Message-ID: <4F432BA7.209@qbik.com>
Date: Tue, 21 Feb 2012 18:29:11 +1300
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120216 Thunderbird/11.0
MIME-Version: 1.0
To: Bron Gondwana <brong@fastmail.fm>
References: <alpine.LSU.2.00.1202161626400.3062@hermes-2.csi.cam.ac.uk><4F3D6E57.8010301@qbk.com><alpine.LSU.2.00.1202171127330.30682@hemes-2.csi.cam.ac.uk><4F3F4F8F.3040601@qbik.co><1329550573.30138.140661038121885@webmail.mesagingengine.com><alpine.LSU.2.00.120219183240.12769@hermes-2.csi.cam.ac.uk><2012021919260.GA11323@launde.brong.net><4F415C07.3040100@qbik.com><20120219220835.GB12549@launde.brong.net><4F417EF5.6030809@qbik.com><20120219233901.GA13600@launde.brong.net> <4F41952B.8020809@qbik.com><1329738117.22774.140661038826265@webmail.messagingengine.com><4F423CE4.5060103@qbik.com><CAD8HnzwaaHjPTwsze0ACOTgPdEUgyrJZ62CDyasxE0ed8rDcA@mail.gmail.com> <16456.1329744434.840052@puncture><1329748535.2585.140661038887405@webmail.messagingengine.com> <16456.1329749037.223665@puncture> <1329749200.5849.140661038894569@webmail.messagingengine.com>
In-Reply-To: <1329749200.5849.140661038894569@webmail.messagingengine.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Subject: Re: [imap5] Feature set? - was Re: 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: Tue, 21 Feb 2012 05:29:25 -0000

presuming you were storing the message in a file on disk, you could 
adopt some sort of meta structure, where the message was a part, and 
envelopes became other parts (and annotations if desired).  This could 
be as simple as putting a length at the start of the message to where 
the envelopes start.  Any sort of structure I'd length-prefix, so you 
can skip data instead of having to scan it.

the server would take care of it all, and clients would just fetch the 
bits they wanted.  Being in a single file would solve issues relating to 
synchronisation / keeping it all together.


On 21/02/2012 3:46 a.m., Bron Gondwana wrote:
>
> On Mon, Feb 20, 2012, at 02:43 PM, Dave Cridland wrote:
>> On Mon Feb 20 14:35:35 2012, Bron Gondwana wrote:
>>> It probably means storing annotations - or at least providing a way
>>> to access this envelope data that smells remarkably like
>>> annotations.
>> No.
>>
>> Store it as a properly modelled transport envelope - no need to turn
>> it into magic soup - that's never worked.
> Fine with me.  It's just yet another axis of data tied to a message, and
> it needs its very own "keywords" or "annotations" as well, presumably, if
> you want to note when it was accepted, or MDNed.
>
> Bron.

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