Bug 53801 - verify a server's conflict handling policy
Summary: verify a server's conflict handling policy
Status: RESOLVED MOVED
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: SyncML (show other bugs)
Version: unspecified
Hardware:
: low enhancement
Assignee: SyncEvolution Community
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-19 19:44 UTC by SyncEvolution Community
Modified: 2018-10-13 12:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Patrick Ohly 2012-08-19 18:56:45 UTC


---- Reported by jingke.zhang@intel.com 2010-04-19 19:44:54 +0000 ----

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.
====================================================



--- Bug imported by patrick.ohly@gmx.de 2012-08-19 20:56 UTC  ---

This bug was previously known as _bug_ 1004 at https://bugs.meego.com/show_bug.cgi?id=1004

Unknown platform unknown. Setting to default platform "".
Unknown operating system unknown. Setting to default OS "".

Comment 1 GitLab Migration User 2018-10-13 12:37:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/libsynthesis/issues/5.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.