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

* Your Email Address
* Spam protection	Enter the letters below: .___..__..___.. ,. . \| \| \| _/ \./ \|__\| \| \|__\|./__. \| \| \|
Comment	> 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.
Attachment
Watch this ticket