[Tickets #12597] Re: AS: Detect deletes on a non-CONDSTORE server

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12597
------------------------------------------------------------------------------
  Ticket             | 12597
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | AS: Detect deletes on a non-CONDSTORE server
  Queue              | Synchronization
  Version            | Git master
  Type               | Enhancement
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-08-22 16:03) wrote:

> For new, empty, folders this would cause the initial sync code to  
> hit on every sync even on CONDSTORE servers - after we already know  
> we don't have changes. I had code similar to this in place (using  
> only modseq == 0 as the final check) once apon a time, but needed to  
> change it due to this issue (and others, IIRC though I'm drawing a  
> blank on what they were).

What kind of modseq value does a CONDSTORE server report
for a new, empty folder?

The current code enters the modseq code path when the stored
$folder->modseq() is higher than zero.
(same problem if we run into the "initial sync" code path)

If it's higher than zero (as your remark above would imply),
then the new, simplified code would behave the same, won't it?