http://bugzilla.meego.com/show_bug.cgi?id=1180
Summary: Funambol, Memotoo, ...: workaround for detached
recurrences
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
OS/Version: IA
Status: ASSIGNED
Severity: normal
Priority: Medium
Component: SyncEvolution
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
CC: [email protected],
[email protected]
Estimated Hours: 0.0
Problem: recurring events are shown twice by web services when modifying
specific instances of it.
Problem was originally discussed in the "[SyncEvolution] UID/RECURRENCE-ID /
detached recurrence / Funambol / Memotoo (was: Re: A synchronization server
named Memotoo)" mail thread.
Root cause: many servers ignore UID and RECURRENCE-ID and thus display
recurring events and detached recurrences incorrectly after sent by
SyncEvolution.
In iCalendar 2.0, detached recurrences are linked to the recurring event
via their UID. If there is a VEVENT with UID=<foo> and
RECURRENCE-ID=<date>, then the main event is not to be displayed on
<date>, only the detached recurrence is.
In addition, some software also adds an EXDATE exception in the main
event for <date>. I don't think this is required.
> > - a detached recurrence on Evolution is duplicated on Memotoo but not
> > on Evolution, even after resync.
>
> This I can reproduce, and it fits my theory. When modifying one
> recurrence, Evolution 2.38.3 did not update the recurring event, so all
> that Memotoo is sent is one VEVENT with UID and RECURRENCE-ID. It then
> ignores the UID and thus displays the main event and the detached
> recurrence.
>
> Thomas, does that make sense? Any suggestions how this could be fixed?
We've had the same problem with Funambol. At that time I didn't have an
idea, but after writing down the explanation above and thinking some
more about it, here's something that might work: when a new VEVENT gets
added in Evolution with RECURRENCE-ID for an existing, unmodified
recurring event, then modify the recurring event by adding an exception.
Then sync both the main event and the child to the server.
Evolution doesn't do this because iCalendar 2.0 doesn't require it, but
as workaround for servers with incomplete iCalendar 2.0 semantic (like
Memotoo and Funambol) it is necessary and should have no negative side
effects (well, except for more complicated client code and slightly
increased network traffic).
--
Configure bugmail: http://bugzilla.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues
