[Kde-pim] iCalendar semantic

[Patrick Ohly]

On Mon, 2014-03-17 at 15:24 +0100, Kevin Krammer wrote:
> 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.

Modifying the UID would lead to duplicates in the calendar. I don't
think that's the right solution.

Bye, Patrick

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