[sync] Trouble keeping SyncML in sync with IMAP store

[Jan Schneider]

>> If some Horde backends require a
>> history update before the actual synchronization, we can initiate such
>> an update from SyncML_Backend_Horde.
>
> Yes, indeed. But that would need to call the API of the database that is
> currently being accessed via SyncML or am I missing something? It might be an
> additional API function rather than listBy() but otherwise the Horde SyncML
> backend would need additional knowledge about the actual storage  
> backend used.

Exactly, that would be a separate API method, that does a noop on  
non-Kolab application backends.

>> Though I can't imagine how this
>> should be reliably working if it doesn't happen right when the data
>> changes.
>
> External modifications to the storage do in some parts violate the  
> Horde History
> concept as the timing of a change can't be precise anymore. For  
> SyncML this does
> not seem to be a problem though as we only ask if there was a change during a
> certain time period. As long as the code ensures that all change  
> timestamps are
> in the correct time periods SyncML is fine. And that should work  
> fine as long as
> SyncML calls storage synchronization right before determining the next anchor
> points for the time period.

If you say so. :) I know less about Kolab's internals than SyncML's so  
I trust you that this is indeed possible.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/