MBOX-Line: From tss at iki.fi  Wed Aug 21 11:55:54 2013
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:51 2018
Subject: [Imap-protocol] Multiple non-waiting UID SEARCH commands
In-Reply-To: <466fa36a-1178-4cba-8cf1-a9111e5aac1a@email.android.com>
References: <520A622E-1A91-4B04-AD6F-361896D439F5@lasselog.com>
	<5214A27E.8030300@isode.com>
	<CAC4RtVDtTBK6EOGtqJNkCQewgc-ZpMMOMq=046j+Umh6H6imvA@mail.gmail.com>
	<466fa36a-1178-4cba-8cf1-a9111e5aac1a@email.android.com>
Message-ID: <C55A479E-9F07-49A7-96F7-1C32463F5B96@iki.fi>

On 21.8.2013, at 21.00, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> wrote:

> From hazy memory: In case of ambiguity, the server must process the commands in the order received?

I think this is the main point of it:

> The exception is if an ambiguity would result because of a command that would affect the results of other commands.

Running two SEARCH commands in reverse order don't affect the results of each others, just the order in which they're received by the client.


