[Tickets #12175] Re: ActiveSync misses changes from history database

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12175
------------------------------------------------------------------------------
  Ticket             | 12175
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | ActiveSync misses changes from history database
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-04-18 16:57) wrote:

> Regarding the fudge factor, if we set it to f.e. ten seconds in the  
> past, that would also mean changes need at least ten seconds until  
> they are visible to the syncing device. Not pretty but much better  
> than data loss.

There is already a built in wait due to the way the sync/heartbeat  
works. So the actual delay with the new code could be anywhere from  
$interval + 0 seconds (if the change occurs right at the end of a  
heartbeat) to $interval + 10 (if it occurs at the end). $interval, by  
default is something like 10 seconds IIRC and is configurable in the  
activesync config.