[Kde-pim] Simultaneous Akonadi collection updates lead to data loss

[David Jarvie]

I've encountered a problem where a collection update using
CollectionModifyJob will overwrite a near simultaneous CollectionModifyJob
from another process. I haven't found any mechanism to prevent this
happening. The two processes in this case are a resource and an
application, but it could equally happen when two applications attempt to
update the same collection.

I've managed to overcome the issue in KAlarm by splitting an attribute
class into two different attribute classes, one which is only changed by
the resource, and the other which is only changed by the application. But
this approach won't prevent the general problem (not restricted to
KAlarm), which is likely to grow in importance as the number of plasmoids
and other applications which access the same Akonadi data is likely to
expand and make such clashes more likely.

-- 
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm

_______________________________________________
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/