[Chandler-dev] Handling email updates in a consistent way

[Brian Kirsch]

Hi Jeffrey,
Thanks for writing up the sequence number proposal.

I would have to disagree with your selection of option A "Continue to  
let the server win, publish sequence number but ignore it when  
syncing, only increment sequence when an email update is sent out."  
as the preferred method.

If I understand option A correctly, then my concern is it requires a  
server i.e. Cosmo. This puts a dependency that a sharing account must  
be created in order to use the mail edit / update features.

Since P2P sharing via mail transports was envisioned as an  
alternative to traditional server based sharing, I don't think  
creating a sharing server dependency makes a lot of sense.

I think option B "Track sequence and date stamp on the server, and  
use the same heuristic for resolving conflicts in server sharing as  
with email" is the way to go because mail and server sharing can  
leverage the same heuristics but function independently of one  
another. The sequence numbers and date stamps for an item would be  
stored in the Repository. These local values would be used by the  
mail layer to determine who wins a conflict. The sharing server layer  
would also user these values to compare the local version against the  
version(s) on the server. Both the mail and sharing layers would use  
the same utility method that when passed two versions of an item will  
determine the winner based on the sequence number and date stamp.

Thoughts?

-Brian


On Dec 4, 2006, at 5:24 PM, Jeffrey Harris wrote:

> Hi Folks,
>
> I wrote up a wiki page describing how we might use a date stamp and a
> sequence number when managing email updates in Chandler, the link is:
>
> http://wiki.osafoundation.org/bin/view/Journal/MultiTransportSharing
>
> Please have a look, especially if you're involved in the email/sharing
> universe.
>
> Sincerely,
> Jeffrey
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev