Tickets :: Comment on [#12175] Add modification sequence support to Horde

* Your Email Address
* Spam protection	Enter the letters below: .___.___.__ .___. . [__ [__ [__) _/ \| [___\| \| ./__.\__\|
Comment	>> 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. > >
Attachment
Watch this ticket