MBOX-Line: From mrc+imap at panda.com  Sat Jun 12 00:29:08 2010
To: imap-protocol@u.washington.edu
From: Mark Crispin <mrc+imap@panda.com>
Date: Fri Jun  8 12:34:44 2018
Subject: [Imap-protocol] IMAP MOVE extension
In-Reply-To: <4C1330B7.9030106@gulbrandsen.priv.no>
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>
	<4C1330B7.9030106@gulbrandsen.priv.no>
Message-ID: <alpine.OSX.2.00.1006120018310.662@hsinghsing.panda.com>

On Sat, 12 Jun 2010, Arnt Gulbrandsen wrote:
> 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.

Sigh.  Once upon a time, the IMAP specification did.

That text triggered a major flame war.  It was the worst in IMAP's history
and nearly derailed IMAP completely.  A certain individual (long vanished
from the scene) was utterly enraged by the idea of a cache.

The only way to stop it was to remove all reference to the cache and cache
fill from the specification.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.

