Hi Phillip, > That sounds good, except that it's not really defined. In the > edit/update case, I could email you a change Morgen made, along with a > change that I made previously (but Morgen's change is later, so my > lastModifiedBy says Morgen). > > Now, if one or both changes conflict with your Chandler, then what do we > do to your lastModifiedBy? Under the model you propose, it is quite > possible to have a situation where, no matter what we do, the value will > be wrong!
I don't follow why the value is wrong here. The lastModifiedBy from the email would be Morgen, because his change was later. If any changes don't conflict, the item changes to say Morgen changed it last. If all changes conflict, the item still says Mimi changed it last. It's true that a particular change you made may look like it was made by Morgen, but I think Mimi's saying that's an acceptable failure mode for preview, so it's not wrong. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
