Hello Thomas!
I am currently testing the following change in SyncEvolution:
commit 662aab0823905d56edf812cf5bf2464379fdfcaf
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Wed Jul 23 14:07:13 2014 +0200
EDS: memo syncing as iCalendar 2.0 (FDO #52714)
When syncing memos with a peer which also supports iCalendar 2.0 as
data format, the engine will now pick iCalendar 2.0 instead of
converting to/from plain text. The advantage is that some additional
properties like start date and categories can also be synchronized.
The code is a lot simpler, too, because the EDS specific iCalendar 2.0
<-> text conversion code can be removed.
With Memotoo that only works partially. Adding a new note on the server
using iCalendar 2.0 as format works. Updating it fails: the server seems
to ignore the new data.
I also noticed that the server sends broken CtCap if (and only if!) the
client mentions iCalendar 2.0. Memotoo then lists
<Rx-Pref><CTType>text/calendar</CTType> and
<Rx><CTType>text/plain</CTType> but then describes some unrelated
<CTCap><CTType>text/x-vnote</CTType>
Here's the sync where a note gets updated:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-m...
First message sent by client:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-m...
Broken CtCap from server:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-m...
Update sent by client:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-m...
This is what a second client then later gets:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-m...
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-m...
For reference, this works correctly when the client only claims to
support plain text:
http://downloads.syncevolution.org/syncevolution/archive/test-results/syn...
http://downloads.syncevolution.org/syncevolution/archive/test-results/syn...
http://downloads.syncevolution.org/syncevolution/archive/test-results/syn...
http://downloads.syncevolution.org/syncevolution/archive/test-results/syn...
--
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.