On Fr, 2011-07-01 at 21:27 +0200, Ove Kåven wrote:
> Den 01. juli 2011 16:12, skrev Patrick Ohly:
> > Trying again with a recent commit like 62239e5c9 would be worthwhile.
>
> Hmm. I think that works (so far).
A random thought struck me yesterday: the slow sync matching of calendar
items is based on the assumption that CalDAV server and local backend
support UIDs. This won't work with the Maemo 5 backend. You'll need to
stick with the traditional approach of comparing properties.
I don't have a configuration mechanism in place for this yet. In the
meantime, can you perhaps patch SyncContext.cpp and comment out the
following code on Maemo 5?
// Choosing between comparing UID/RECURRENCE-ID vs. other
// iCalendar 2.0 properties is a hack: in local sync mode, the
// iCalendar 2.0 semantic is always picked.
if (m_serverMode && m_localSync) {
SharedKey sessionKey = m_engine.OpenSessionKey(session);
SharedKey contextKey = m_engine.OpenKeyByPath(sessionKey,
"/sessionvars");
m_engine.SetInt32Value(contextKey,
"VCALENDAR_COMPARE_UID",
true);
}
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
