[#6657] Allow SyncML conflict resolution by duplication
Summary Allow SyncML conflict resolution by duplication
Queue SyncML
Type Enhancement
State Assigned
Priority 1. Low
Owners Karsten Fourmont <karsten (at) horde (dot) org>, Jan Schneider <jan (at) horde (dot) org>
Requester Gunnar Wrobel <p (at) rdus (dot) de>
Created 04/28/2008 (71 days ago)
Due
Updated 05/07/2008 (62 days ago)
Assigned 05/01/2008 (68 days ago)
Resolved
Attachments HK-GW-SyncML_conflicts.patch Download
HK-GW-SyncML_conflicts[1].patch Download
Milestone
Patch Yes

History
05/07/2008 Gunnar Wrobel Comment #2
New Attachment: HK-GW-SyncML_conflicts[1].patch Download		 Reply to this comment
Updated patch to current CVS HEAD.
05/02/2008 Jan Schneider Patch ⇒ 1
 
05/01/2008 Chuck Hagenbuch State ⇒ Assigned
 
04/28/2008 Gunnar Wrobel Assigned to Karsten Fourmont
Assigned to Jan Schneider
 
04/28/2008 Gunnar Wrobel Comment #1
New Attachment: HK-GW-SyncML_conflicts.patch Download
Patch ⇒
Milestone ⇒
Queue ⇒ SyncML
Summary ⇒ Allow SyncML conflict resolution by duplication
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New		 Reply to this comment
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.