[Design] Updating share items results in false positive conflicts

[Mimi Yin]

On Oct 1, 2007, at 11:35 AM, Morgen Sagen wrote:

>> 2. Capture and send the 'last synced version' of an item when  
>> sending it out
>> via email so that Chandler Desktop recipients can tell if the  
>> sender/updater
>> edited the same version of the item they have.
>
> I don't think this is something that can be solved by only changing
> the way edit/update works because that would just solve the case where
> the item is received via sharing prior to receiving a different copy
> via email.  If the order were reversed and the item arrived via email
> and then a different copy arrived via sharing, the differcences would
> still be in conflict.

Morgen, when would this happen? When would the sharing sync version  
of the item be different from the email version?

In the example with Philippe's update, the updated version was the  
same as the one Jeffrey would receive via sharing sync. So there  
wouldn't have been a conflict.

If Philippe edited the item again and synced, would Jeffrey's  
Chandler be able to tell that Philippe had edited the version J  
received via email?

> You can even get these conflicts for an item in
> two shared collections without involving email:  if you are sharing
> collections A and B with me and an item is in A, but I copy it to B
> and make a change, then you sync only collection B, any changes I made
> will be in conflict on your item until you sync A (at which point the
> conflicts will disappear automatically). This is not a scenario people
> are likely to run into.

Sorry, I'm not understanding the item in 2 shared collections thing.

>
> So I am thinking that if I fix bug 10877 that will at least make the
> problem less likely to appear.

This is definitely a good start. We may not need to do more than this.

> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Design" mailing list
> http://lists.osafoundation.org/mailman/listinfo/design