Re: [SyncEvolution] Sync issue server ->client
On Fr, 2010-11-05 at 09:33 +0000, Nils Faerber wrote:
Am 04.11.2010 20:59, schrieb Patrick Ohly:
> On Do, 2010-11-04 at 17:58 +0000, Nils Faerber wrote:
[...]
>> I have to admit I have never ever seen or heard about
"text/x-s4j-sifc"
>> so I have no clue what this is about.
>
> The Horde server is not configured correctly. It sends the client
> calendar data in an out-dated Funambol XML format.
Does this also apply to the contacts? Because the same happens with
contacts - N900->Horde works, but not in the other direction.
That might be the same problem.
Now here comes my ignorance: I read "between" the lines
here on the
mailinglist that basically Syncevolution negotiates dataformats and
profiles with the syncml partner. There also are config options in the
sync sources (like calendar) to hardy-fix some of those formats (like
using icalendar V2.something).
SyncEvolution/Synthesis support that, but Horde doesn't. It basically
detects the peer and then picks one format for sending. That goes wrong
here.
Is there probably something that I can do on the N900 side to force
Horde into another mode?
You might check your deviceId. That was a workaround that worked a while
ago, but it should be in the code. Hmm, perhaps the N900 port still has
that problem? The workaround was released as part of 1.0 beta 2.
commit 185a33d3415a6156c9bcf7ee120566aa9b91983a
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Fri Feb 19 16:13:43 2010 +0100
deviceId: use syncevolution- prefix, helps Horde (MB #9347)
Previously we used "sc-pim-" as prefix for our device ID because
my.FUNAMBOL depended on it for distinguishing phones from other
devices. It supported only one phone, but multiple others. Without
the right prefix it would do slow syncs when switching between
different clients.
This behavior was changed, which allows us to use our own prefix.
That solves a problem with Horde, which treated our client like
an old, broken Funambol client because of the prefix and then
sent us calendar items in the old Funambol SIF-C format instead
of vCalendar/iCalendar.
Released as part of 1.0 beta 2.
--
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.