[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         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | ActiveSync misses changes from history database
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2013-04-18 07:24) wrote:

> So, we'd need to add new methods to both  
> Horde_Core_ActiveSync_Driver, Horde_Core_ActiveSync_Connector and  
> EACH groupware application's API, and each library would need to  
> perform multiple is_callable() checks to sniff out what data to  
> present.  What happens if somebody upgrades only Turba, for example,  
> and not Kronolith? We'd have a mix of timestamps and counters with  
> no real way for the AS library to know which we need to store/send.  
> This is a REALLY ugly solution.

Yep, that's really messy. So let's go the fudge factor route for the  
current release and implement this in a new branch to be merged for 6.0.

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.