[Kde-pim] Changing UID of a newly created Akonadi::Item

[Kevin Krammer]

On Thursday, 2011-11-24, Dan Vratil wrote:
> On Thursday, November 24, 2011 10:41:16 Kevin Krammer wrote:
> > On Thursday, 2011-11-24, Dan Vratil wrote:

> > > The problem with payload UID is that when user changes the event via
> > > Google Calendar web interface and then synchronizes the resource, the
> > > UID is updated as well together with the other informations . And
> > > that's not OK, I think that UID should remain constant for the lifetime
> > > of the event, not changed after first synchronization.
> > 
> > But in this case changing the UID in itemAdded() would just do that, no?
> 
> Yes, but I change it when the item is created, so at the very beginning of
> it's existence when nobody minds :). Until now the UID changed after user
> modified the event in Google and the resource had fetched the update, which
> is much worse situation.

Hmm. That assumes that the resource is online at the time of event creation so 
basically any "reader" will see the new event and almost instantaniously see 
the update. Which is not necessarily true of the resource is offline.

Anyway, clients should probably not be concerned toomuch about payload 
internal UIDs or their stability, the Akonadi item ID won't change due to any 
changes to the item.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- 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/20111125/3304b96c/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/