Re: draft-melnikov-imap-search-res

[Alexey Melnikov <[e-mail]>]

Mark Crispin wrote:

> The problem is when the search result is long and sparse, meaning that 
> it can not be collapsed easily with range syntax.  With large enough 
> mailboxes, the result is a command which is larger than the maximum 
> command length, and thus the command needs to be broken up into 
> multiple commands (which in turn creates its own problems).
>
> I don't particularly like "<<", since it implies some sort of UNIX 
> like piping (and implications can cause a lot of problems!), and 
> suggest something like "$" or even an atom (such as "LASTSEARCH") instead.

I will change it to "$", thanks.

> One possibly messy consequence is if this is allowed in a SEARCH 
> command; this would AND previous search results with addition criteria.

One can also OR it, e.g.

a SEARCH <<,90:120

>   I can see why people may want to do that.  However, with complex 
> SEARCHes, especially using IMAP4-style nesting, this can get extremely 
> complicated.

Alexey