MBOX-Line: From arnt at gulbrandsen.priv.no  Sat Jun 12 00:01:11 2010
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun  8 12:34:44 2018
Subject: [Imap-protocol] IMAP MOVE extension
In-Reply-To: <alpine.OSX.2.00.1006111724100.662@hsinghsing.panda.com>
References: <1768814180.483.1276267238967.JavaMail.root@dogfood.zimbra.com>
	<1276267479.22134.102.camel@kurkku.sapo.corppt.com>
	<alpine.OSX.2.00.1006110910440.662@hsinghsing.panda.com>
	<1276274718.22134.138.camel@kurkku.sapo.corppt.com>
	<30B328B7-4D1B-4C7E-96CA-E37F7919E2A6@iki.fi>
	<alpine.OSX.2.00.1006111603200.662@hsinghsing.panda.com>
	<4C12CACB.7030205@aol.com>
	<alpine.BSO.2.00.1006111652100.28689@vanye.sendmail.com>
	<alpine.OSX.2.00.1006111724100.662@hsinghsing.panda.com>
Message-ID: <4C1330B7.9030106@gulbrandsen.priv.no>

On 06/12/2010 02:24 AM, Mark Crispin wrote:
> On Fri, 11 Jun 2010, Philip Guenther wrote:
>> The core bits of IMAP are that of a cache fill protocol.
>
> Unfortunately most people do not understand that.

Aside: They might understand it better if the RFC were to mention 
phrases like "cache" and "cache fill protocol" here and there, and talk 
more about such usage of the protocol, and less about other usage.

In general, this thread seems to be turning away from an extension 
client authors want and (in the guise of xaol-move) use, to something 
rather different.

Arnt

