Re: CONDSTORE: STORE UNCHANGEDSINCE 0

[Alexey Melnikov <alexey.melnikov@xxxxxxxxx>]

Timo Sirainen wrote:

> On Mar 13, 2008, at 5:57 PM, Alexey Melnikov wrote:
>
> > Timo Sirainen wrote:
> >
> > > What happened to this?
> >
> > I need to publish CONDSTOREbis draft at some point which contains  
> > the fix. I don't have time or energy to do this now. I should find  
> > some time once all my Lemonade drafts are approved for publication.
>
> Are there going to be other changes? The main problem I currently 
> have  implementing CONDSTORE is that I'd rather not want to figure 
> out  HIGHESTMODSEQ value when selecting a mailbox unless I know the 
> client  wants to use CONDSTORE. I started to wonder if it would work 
> nicely if  a SELECT mailbox returned [NOMODSEQ] but the first 
> CONDSTORE enabling  command would cause * OK [HIGHESTMODSEQ n] to be 
> sent.

That should be Ok, especially if clients try to use "ENABLE QRESYNC" or 
"ENABLE CONDSTORE".

However I don't think a client that sees NOMODSEQ is going to issue any 
CONDSTORE enabling command.

> Which also brings to my mind.. I didn't really understand why the * 
> OK  [HIGHESTMODSEQ n] would be sent again after it was already sent as 
> a  reply to SELECT. This is described in the spec example 5 and also  
> happens in your implementation.

Because HIGHESTMODSEQ might have changed between the moment when the 
mailbox was opened and the moment when the client issued a CONDSTORE 
enabling command.