On Fri, 2003-02-21 at 01:56, Mark Crispin wrote:On Thu, 21 Feb 2003, Timo Sirainen wrote: > "..a server MAY begin processing another command before processing the > current command to completion.." > > I hope that doesn't mean that it can send anything back to client before > other commands have been processed?
As I read RFC 2060, the server can legally do that, and section 5.5 ensures that no ambiguities result.
A server can send anything at any time, and clients must be prepared to accept such.
I meant mostly that could it send reply to first command before the other? That could get pretty confusing with getting LIST or SEARCH replies in different order than expected. Or even mix the LIST replies together.
There are odd limits on what a client can send at the same time. For example, a client can't send two (UID) SEARCH commands at the same time, because the result would be ambiguous. Section 5.5, second paragraph, second sentence.
Or is that possible and client just shouldn't ask things it can't handle correctly?
The RFC actually specifies what the client can and cannot send. Sometimes there are bad choices in there and some of the language could be clearer, but if you read the RFC closely enough it does seem to be fully specified.
--Arnt
