On Mi, 2010-02-17 at 11:35 +0000, Jussi Kukkonen wrote: > Jussi Kukkonen wrote: > > 3. calendar+todo syncs fine otherwise, but the client will return 500 to > > any "Replace" commands, so server side modifications do not work at the > > moment. As far as I can see this only happens to Replace and only on > > calendar+todo. > > This turned out to be another symptom of the <CTCap> problem mentioned > in this same thread. The <showctcapproperties>-trick makes Replaces work > as well.
At least it has something to do with the capabilities. I don't think we have any X- properties in the vcalendar profile; we'd have to check more carefully which property it is that the device stumbles over. > Lukas, do you have a vision on how and where this should be fixed properly? One solution would be to never send any capabilities for the device, based on a remote rule. This is the sledgehammer approach. The other solution would be to disable certain properties and/or parameters, again based on a remote rule. This is a lot more work and would require changes to the profile mechanism/configuration: first, we need the ability to activate multiple rules, not just one as supported now. This is something we already discussed and found useful elsewhere. Second, we need that for parameters (X-EVOLUTION-SLOT). Right now, only properties can be controlled like that. I'm a bit afraid about taking the second path. Lukas, comments? -- 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
