Hello Santosh! Thanks for the detailed explanation.
On Di, 2010-11-09 at 05:36 +0000, Santosh Puranik wrote: > ext Patrick Ohly wrote, On Friday 05 November 2010 02:36 PM, UTC +0530: > > The much simpler question is: how should the OVI.com problem be fixed in > > MeeGo? Modify /etc/sync/meego-syncml-conf.xml to have > > omit-data-update-status == 1 and use that for all SyncML peers? > > You can do that. From our testing with Google, and Memotoo, the setting > has no impact on clients other than ovi.com, as they require a response > for package #4. So the only remaining question is about who will make that change. I don't know how the Buteo team has split the responsibilities between SyncML developers and sync client plugin, but my expectation is that either one or the other updates meego-syncml-conf.xml. It's currently in the buteo-syncml repo and package, so I would have expected that it gets set to the desired value right away, together with introducing it. -- 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. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
