[Kde-pim] Synchronization support for Akonadi

[Patrick Ohly]

On Tue, 2009-10-20 at 12:32 +0200, Ingo Klöcker wrote:
> I'm wondering whether it wouldn't be better if each sync app would 
> provide its own custom tailored SLA. Of course, we could provide a 
> primitive SLA that could be used as template, but I doubt that we can 
> provide an SLA that fits the need of all sync apps.

I second that. In SyncEvolution, I originally used the change tracking
support provided by Evolution Data Server. It didn't quite fit the needs
of SyncML, so eventually I replaced it with change tracking based on the
REV (vCard) and LAST-MODIFIED (iCalendar) properties.

If Akonadi has efficient retrieval of ID/modification stamp pairs for
all items in a database (and its my understanding that it has), then
that's all that is needed for SyncEvolution and plugs nicely into the
TrackingSyncSource.

If you really want to add something, here are some points to consider:
      * Depending on time stamps - is time 100% guaranteed to be linear?
        Not in my experience.
      * Keeping a log that is shared by apps. How do you know when old
        entries are no longer needed? If you don't, the log will grow
        infinitely.
      * Keeping one log per app (as EDS does) that is flushed by the
        app. Who deletes the log when the app gets uninstalled?

-- 
Bye, Patrick Ohly
--  
Patrick.Ohly at gmx.de
http://www.estamos.de/


_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/