[Kde-pim] iCalendar semantic

[Kevin Krammer]

On Monday, 2014-03-17, 15:15:17, Christian Mollekopf wrote:
> On Monday 17 March 2014 14.27:26 Kevin Krammer wrote:
> > On Monday, 2014-03-17, 14:17:24, Christian Mollekopf wrote:
> > > The resource has only very limited possibilities in treating errors
> > > since the client operation is already complete, so it basically can only
> > > drop an operation instead of writing it to the backend.
> > 
> > The resource can always modify the data if it needs to, no?
> 
> Sure, if the resource can automatically fix the problem and this doesn't
> lead to unexpected side effects that is a possibility. I think it should be
> avoided as far as possible because you'd want the correction to immediately
> happen. Otherwise e.g. an invalid event gets modified at some random point
> in time (when the resource tries to synchronize), instead of when the user
> modified the event, and IMO that results in a rather unexpected user
> experience.

Sure. I was mainly thinking about the case when a new item is added and the 
resource finds a UID collision. It would then modify the UID before writing to 
the backend and modify the item accordingly.

A really new item would have a new UID, but the add could come from a copy 
operation, not from a client manually creating payload copies and ensuring 
their ID uniqueness.

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/20140317/61c74c0c/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/