Hi Phillip, Moving this piece of the discussion (about design) to the design list.
> Note that knowing who made the last change is not the same as knowing > who you have a conflict with. The approach I proposed (of simply > keeping the most-recent last-modified-by user+date) actually ensures > that we always have a correct answer for "who last changed the record" > -- *whether their changes were applied or not*. > > So, by that definition, the conflict-free approach is 100% correct all > the time. Whether that's actually what we *want* is a separate > question. :) I think what we want for the UI is to change lastModifiedBy (which correspond in the UI to created by/edited by) if any changes successfully merge in or if conflicting changes are accepted, but not to change lastModifiedBy if all changes are conflicting and the conflict either hasn't been resolved or local changes are chosen to win. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
