[Tickets #6657] Re: Allow SyncML conflict resolution by duplication

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6657
------------------------------------------------------------------------------
  Ticket             | 6657
  Updated By         | Jan Schneider <jan at horde.org>
  Summary            | Allow SyncML conflict resolution by duplication
  Queue              | SyncML
  Type               | Enhancement
-State              | Assigned
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
-Owners             | Karsten Fourmont, Jan Schneider
+Owners             | Jan Schneider
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2009-01-10 08:10) wrote:

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.