[#6657] Allow SyncML conflict resolution by duplication
Summary Allow SyncML conflict resolution by duplication
Queue Synchronization
Queue Version Git master
Type Enhancement
State Assigned
Priority 1. Low
Owners wrobel@horde.org
Requester wrobel@horde.org
Created 2008-04-28 (4735 days ago)
Updated 2010-10-24 (3826 days ago)
Assigned 2009-01-12 (4476 days ago)
Patch No

Gunnar Wrobel <wrobel@horde.org> 2008-04-28 07:56:56
The SyncML module in Horde responds to a conflict situation (item 
edited on both the server and the client since the last 
synchronization) with "first synchronization wins". This means the 
client will usually overwrite any modifications done on the server as 
the client usually synchs first during a synchronization run.

The attached patch will respond to such conflicts with a duplication 
of the conflicting element. I believe this is preferable over possible 
data loss. If necessary it could also be made configurable.

Gunnar Wrobel <wrobel@horde.org> 2008-05-07 13:22:37
Updated patch to current CVS HEAD.

Jan Schneider <jan@horde.org> 2009-01-10 13:10:20
Taking a closer look at this patch, I can't accept it with the current 
implementation. Reason is, that it does yet another request to the 
backend for every single client change. Synchronization already puts a 
high load on the backend and I don't want to even worse it. Especially 
since we retrieve the information about server changes anyway, at 
least during two-way-syncs.

That's another point, only two-way-syncs can create conflicts, so we 
should only check for them in this case. OTOH, we only retrieve both 
server and client changes in two-way-syncs, so it might be sufficient 
to simply compare them.

Gunnar Wrobel <wrobel@horde.org> 2009-01-11 22:29:57
Make sense. I know I can't respond to this within two weeks. Can you 
assign it to me so that I have it on my long term ToDo list?