MBOX-Line: From snowjn at aol.com  Thu May 26 13:35:12 2011
To: imap-protocol@u.washington.edu
From: John Snow <snowjn@aol.com>
Date: Fri Jun  8 12:34:46 2018
Subject: [Imap-protocol] History question.
In-Reply-To: <alpine.OSX.2.00.1105261223590.973@hsinghsing.panda.com>
References: <4DDEA412.6030305@aol.com>
	<alpine.OSX.2.00.1105261223590.973@hsinghsing.panda.com>
Message-ID: <4DDEB980.4010806@aol.com>

Mark Crispin wrote:
> On Thu, 26 May 2011, John Snow wrote:
>> My question is simply, why?  Why is the sequence number needed when the
>> command specified a UID, and the UID must be included in the response.
>> Seems to me the UID command should have a UID response.
>
> You have already asked this "question" many times.
I may have, I don't remember.  I do remember asking how other servers 
deal with MSNs on a large mailbox.  I  remember saying I'd be happy for 
MSNs to go away.  I don't remember ever asking how it was decided.

I don't expect that my question is going to change the protocol.  I was 
just wondering why the UID command doesn't have a matching UID 
response.  I assume there was some big discussion when this was hammered 
out and wondered what the reasoning might have been.
>
> Clients that use only UIDs and disregard message sequence numbers are
> doomed to suck.
>
maybe, but I don't think it guaranteed. 
> IMAP can not prevent the creation of clients that suck; but it will
> nonetheless continue to enable the creation of clients that do not suck.
>
> Nor will IMAP repeat the UID SEARCH command's mistake of command modality
> in response interpretation.
>
> -- 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.
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20110526/c47cc391/attachment.html>
