[Kde-pim] Synchronization support for Akonadi

[Thomas McGuire]

Hi,

On Tuesday 20 October 2009 16:18:03 Sascha Peilicke 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.
> 
> This seems to be what is currently done in some places, but has some
>  serious  drawbacks. What happens when Agents crash or when the internal
>  Akonadi database is getting reorganized (backend change for example)? The
>  agent would have to take track of each and everything, which is actually
>  the role of the Akonadi server. Furthermore we would have multiple storage
>  places again. And how should an Agent do that? Using a personal database
>  to guarantee integrity?

I agree that the current way to record notifications is not optimal, because 
of crashes etc, like you mentioned.
Server-side change recording would solve this problem. In addition to that, we 
could add timestamps to the notifications. With both those things in place, 
that should provide what sync support need.
But then, I already tried to nudge Volker into implementing and he doesn't 
have the time. Neither do I, currently.

Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20091020/a8207168/attachment.sig>
-------------- next part --------------
_______________________________________________
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/