[Kde-pim] Two Akonadi ItemModifyJobs clashing

Volker Krause vkrause at kde.org
Fri Sep 10 08:22:28 BST 2010


On Friday 10 September 2010 08:52:29 David Jarvie wrote:
> When two instances of ItemModifyJob are created in quick succession for the
> same Akonadi Item, the conflict resolution dialog is displayed. This
> happens even if creation of the second ItemModifyJob is delayed until the
> result slot from the first job is called. How is it possible to ensure that
> the two jobs don't clash?

just delaying it is not enough, there are basically two ways to avoid the 
conflict:
- make sure the second job has the update item revision number provided by the 
first one (see Item::revision()), that's what is used to detect the conflict 
in the first place.
- disable conflict detection (ItemModifyJob::disableRevisionCheck() IIRC), 
obviously not the preferred way in general, but can be useful in some 
situations where you only modify application internal properties for example.

regards
Volker


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100910/1fc44457/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/


More information about the kde-pim mailing list