--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2009-07-31 00:07:05 ---
(In reply to comment #5)
(In reply to comment #3)
> (In reply to comment #2)
> > You're correct. I think you're asking me to verify this. So:
> > ScheduleWorld is configured to be 'client wins'.
> I don't think that this is a useful policy for delete/update conflicts because
> data can get lost. I have added it as a caveat to the new
> test/README.scheduleworld document:
> ScheduleWorld resolves conflicts where the client deleted an item that
> was updated on the server by deleting the item on the server (Bugzilla
> #4369). Advice: copy items instead of updating them if they were
> deleted elsewhere, otherwise the updated item may get lost later on.
> If you think changing the policy would be useful, then let's reopen this issue.
I think it would be fair to also state the reverse for servers configured for
'server wins'. F.E. the server has the 'delete' and the client has the
the client will lose the update on the next sync.
That's correct. "sever wins" for a client update/server delete conflict
Mark, you seem to think that only "server wins" and "client wins" are
choices in this case. But there's a third one: the right conflict resolution
IMHO would be to keep the updated item.
I'm assuming other servers
that use 'server wins' do this. Am I wrong?
I hope they don't. Do you know of a server who does it like that?
I have checked with Synthesis and Funambol. Both preserve the updated item in
both cases, exactly as I would expect it. I have updated the
README.scheduleworld to document this new information and enhanced the advice:
ScheduleWorld resolves conflicts where the client deleted an item that
was updated on the server by deleting the item on the server (Bugzilla
#4369). Other servers always preserve the updated item in an update/delete
conflict, regardless which side has the update.
Advice: always sync before making changes. If it is too late for that,
copy items instead of updating them if they were deleted elsewhere,
otherwise the updated item may get lost later on.
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.