Re: [imapext] CONDSTORE interaction with SORT/THREAD

[Alexey Melnikov <[e-mail]>]

On 13/08/2013 20:14, Timo Sirainen wrote:
> On 13.8.2013, at 19.57, Alexey Melnikov<[e-mail]>  wrote:
>>>> 1). Use ESEARCH response (RFC 4731) to return MODSEQ for all matching messages and also extend it to return sorted results. (This can be potentially be used for SEARCH with MODSEQ search criterion as well). For example:
>>>>
>>>> * ESEARCH (TAG "A001") SORTED 3,4,1,2 MODSEQ 175
>>> One possibility would be to return #1, but only if some other new parameter is used. That parameter could then also be used without MODSEQ. It also wouldn't break with the existing Dovecot installations.
>> Right. For example RESMODSEQ (it has the same semantics as MODSEQ SEARCH/SORT item, but causes ESEARCH response to be returned).
> I was thinking ESORT compatibility, but then of course ESORT would have to be implemented also by the server. But if we're talking about using ESEARCH anyway, it should be a minor job for servers to add support for ESORT. This actually already works:
>
> a SORT RETURN (ALL) (DATE) UTF-8 MODSEQ 1234
> * ESEARCH (TAG "a") ALL 5,3,2,1 MODSEQ 1236
Ok. I've added this example to the draft.

>>>> Similarly, for THREAD:
>>>>
>>>> 1). Use ESEARCH response (RFC 4731) to return MODSEQ for all matching messages and also extend it to return threaded results. For example:
>>>>
>>>> * ESEARCH (TAG "A002") THREAD ((2)(3 6 (4 23)(44 7 96))) MODSEQ 909240921
>>>>
>>>> Here again, I prefer choices #1/#3.
>>> With THREAD Dovecot doesn't return MODSEQ in any way.
>> Ok. Which option you prefer for THREAD+CONDSTORE?
> Something similar to the ESORT example I think (so #1 reply with some parameter to switch on ESEARCH reply mode).
For now I added sentence that THREAD+CONDSTORE don't return MODSEQ for 
matching messages, as at least 2 server implementations didn't implement 
this (yours and mine). If people object, I can change that.