http://bugzilla.moblin.org/show_bug.cgi?id=5635
--- Comment #27 from Thomas Pequet <[email protected]> 2009-09-19 02:43:04 --- (In reply to comment #22) > Thomas, > A new issue is raised. When server alerts a '200' two-way sync, the server > misses a 'Last' element, which is used to be compared for the use of anchor > matching. I could confirm that this issue didn't occur on Sep 10th. It should > be a new bug in recent days. Thomas, could you help check it please? > The part of the server incoming SyncML message: > <Alert> > <CmdID>6</CmdID> > <Data>200</Data> > <Item> > <Target> > <LocURI>./vcard21</LocURI> > </Target> > <Source> > <LocURI>con</LocURI> > </Source> > <Meta> > <Anchor> ---> should have a child "<Last>" element to make anchors matched > with last sync > <Next>1253195512000</Next> > </Anchor> > <MaxObjSize>1000000</MaxObjSize> > </Meta> > </Item> > </Alert> > > Below is the subpart of a server SyncML message before Sep 10th. > > <Alert> > <CmdID>6</CmdID> > <Data>200</Data> > <Item> > <Target> > <LocURI>./vcard21</LocURI> > </Target> > <Source><LocURI>con</LocURI></Source> > <Meta> > <Anchor xmlns='syncml:metinf'> > <Last>20090904T075939Z</Last> --- Here is the 'Last' anchor element > <Next>20090904T075943Z</Next> > </Anchor></Meta></Item></Alert> Ok now sorry for this problem -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
