On Thu, 2012-10-11 at 12:27 +0200, Lukas Zeller wrote:
> Hi Patrick,
>
> I found that some servers don't like the sync mode extensions in the
> devInf you introduced for SyncEvolution a while ago (crash syncs with
> misleading errors as apparently their wbxml decoders fail or
> something).
>
> As I see no way to automatically control this, I added a session level
> config flag <syncmodeextensions> that must be set explicitly to enable
> the extensions. The default is off, to make sure current libsynthesis
> (master branch) users will no see any difference in behaviour once
> they update. For SyncEvolution, you need to add this flag to your
> config.
For SyncEvolution 1.3.99.3, I've extended the SyncEvolution
"SyncMLVersion" setting to control whether the extensions are enabled.
They are enabled by default because I don't expect many users to use
affected servers, whereas more user will want it on for use with
SyncEvolution as server.
I had already done this a while ago, but then noticed a problem during
release testing which caused me to back out the changes again because I
didn't have time to investigate.
It turned out that I didn't enable the feature on the server side.
Strictly speaking, that shouldn't be necessary, because the server will
only add the extensions when the client already sent his, so there
should not be any problem. But it makes sense to have this configurable,
just in case.
The master branch of libsynthesis on freedesktop.org is now based on the
latest gitorious master branch. Lukas, it contains two patches which you
might want to include:
commit 9b0c01cf2fff6701bdb026518048fc4b06a7072e
Author: Patrick Ohly <patrick.o...@intel.com>
Date: Thu Feb 21 00:51:53 2013 -0800
caching mode: fix memory leak
When deleting unmatched local sync items, the TSyncItem instance was
leaked after removing it from fItems.
commit 99159e0991664f8c8319e634598ea6c9bd73fcc2
Author: Patrick Ohly <patrick.o...@intel.com>
Date: Mon Sep 10 09:15:20 2012 +0200
autotools: bumped minor version
Bumped minor version so that SyncEvolution can ensure that the version
it is compiled against really fixes the VJOURNAL<->plain text
conversion problem.
BTW, did you tag 3.4.0.47? There is a comment about the version, but not
the tag itself.
--
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.
_______________________________________________
os-libsynthesis mailing list
os-libsynthesis@synthesis.ch
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
