[sync] Client and server timestamps don't match

[Karsten Fourmont]

Hi,

 > Not what it means. A syncml 'anchor' is an arbitrary value describing
 > "the point at which the last sync occurred" -
Exactly.

Different sync anchors have nothing to do with different clock times.
They can occur when one partner considers a sync "finished" and stores 
the sync anchor while another considers it "incomplete" and does not 
store the anchor

Jochem, are you using the current cvs version of the Sync module?

Cheers,
  Karsten


Andrew Suffield wrote:
> On Thu, Mar 08, 2007 at 02:16:45PM +0100, jochem at mondrian-it.nl wrote:
>> While testing the funambol windows mobile pluging 3.0.31 against horde's
>> syncml backend, I get the following INFO level entry in the log:
>>
>> client requested sync with anchor ts 16252726 but server has
>> timestamp16232634 on file. Enforcing SlowSync
>>
>> The time on the PDA and the server are (almost, only a few seconds off)
>> identical, and I've waited long enough between syncs to rule out that the
>> small difference might be a problem. 
> 
> Not what it means. A syncml 'anchor' is an arbitrary value describing
> "the point at which the last sync occurred" - it's usually the time in
> seconds, but there's no particular reason why it should be and clock
> differences are not an issue. The server just records the last value
> that the client sent it.
> 
> When the client anchor is higher than the one recorded on the server,
> that indicates the client has synced with something else since it last
> synced with this server (or something is broken).