http://bugzilla.moblin.org/show_bug.cgi?id=4774

           Summary: verify a server's conflict handling policy
    Classification: Moblin Projects
           Product: SyncEvolution
           Version: upstream
          Platform: Generic
        OS/Version: Other
            Status: ASSIGNED
          Severity: normal
          Priority: P3
         Component: * Feature Request
        AssignedTo: [email protected]
        ReportedBy: [email protected]
                CC: [email protected], [email protected]
        Depends on: 4369


As described in bug #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.


+++ This bug was initially created as a clone of Bug #4369 +++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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.moblin.org/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.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to