On Thu, 2012-06-07 at 14:43 +0200, Lukas Zeller wrote: > Just changing getSyncStateAlertCode() call with the second argument > set to false does the same trick. Because that second parameter > switches between "simplified" (true) and "standard conformant" (false) > client alert codes already.
Ah, now I see what that parameter does. I've added a configuration option, as you suggested. It turned out that I was overly optimistic about all current servers supporting it: of course, Google didn't bother supporting refresh-from-server. Unfortunately one cannot use DevInf+remote rules to trigger the right behavior, because the Alert is generated before DevInf is available. Grr. Looks like I will have to introduce a SyncEvolution configure option for this. -- 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
