> Indeed, no apparent relevant difference stands out. Perhaps there is > some difference outside of the message content itself? Maybe. > Do both programs > use the same message encoding (should be WBXML for SyncEvolution)? Yes, because Google only supports WBXML. > the HTTP POST from Buteo going to the redirected URL? Yes, previously it is failed in http error '404'. > If that's all the same, then I only see one possible approach: minimize > the differences until it succeeds. Yes, I'm trying do this.
Thanks for your comments. Cheers, Yongsheng > -----Original Message----- > From: Ohly, Patrick > Sent: Wednesday, October 13, 2010 5:29 PM > To: Zhu, Yongsheng > Cc: Sateesh Kavuri; [email protected] > Subject: Re: Trying to sync Buteo with Google > > On Wed, 2010-10-13 at 09:42 +0100, Zhu, Yongsheng wrote: > > Hi, Sateesh & Patrick > > I'm working on trying to sync Buteo with Google service via SyncML > protocol. Currently it's blocked > > because Google service sends 'unauthorized' error. See the attached > syncML messages "buteo-msgs.zip". > > Since SyncEvolution can sync with Google correctly, as a reference, I also > dump its SyncML messages. > > I'm so curious about this since two messages from Buteo and > SyncEvolution are almost same. > > Indeed, no apparent relevant difference stands out. Perhaps there is > some difference outside of the message content itself? Do both programs > use the same message encoding (should be WBXML for SyncEvolution)? Is > the HTTP POST from Buteo going to the redirected URL? > > If that's all the same, then I only see one possible approach: minimize > the differences until it succeeds. > > Sateesh, you said that the Google config hasn't been included yet > because not enough testing was done. Has any testing been done? Did you > get past the authentication problem? > > -- > 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 [email protected] http://lists.meego.com/listinfo/meego-dev
