http://bugzilla.meego.com/show_bug.cgi?id=1004 Summary: verify a server's conflict handling policy Classification: MeeGo Projects Product: SyncEvolution Version: unspecified Platform: Netbook OS/Version: IA Status: ASSIGNED Severity: enhancement Priority: Low Component: SyncML AssignedTo: syncevolution-bugs(a)meego.bugs ReportedBy: jingke.zhang(a)intel.com QAContact: jingke.zhang(a)intel.com CC: syncevolution-bugs(a)meego.bugs, syncevolution-syncml-bugs(a)meego.bugs Estimated Hours: 0.0 This is from http://bugzilla.moblin.org/show_bug.cgi?id=4774 Description From pohly 2009-07-27 01:32:38 PST (-) [reply] As described in BMO#4369, conflict handling can vary considerably between servers. It would be useful to include tests in client-test which simulate the various conflicts and identify how the server resolves them. Then for known servers, we could also check whether the current result a) is sane and b) is the one wanted by the server developers. This may be overkill for all of the servers we test with, but for our own we would definitely need this. When I tried the following test with scheduleworld, I see that the policy is “client-win”, contact information is deleted on server. But with funambol, the updated contact A is synced to client. Can you please check which policy should we follow? ==================================================== Test Step: 1. add contact A on client, try two-way sync with server. 2. delete contact A on client, and update contact A on server. 3. try two-way sync. ==================================================== -- Configure bugmail: http://bugzilla.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.