FYI -- summarizing a recent virtual meeting about sharing
In the current sharing implementation, I make the repository do the heavy lifting when it comes to checking for conflicts and dealing with merges. This involves rewinding a repository view to the point in time of the last sync, then downloading/applying changes from the server, and merging in local changes by doing a refresh( ). This mostly works, although we've discovered it can be quite slow refreshing through a lot of views.
So after discussing this with the engineers directly affected, at the beginning of alpha5 development I will streamline this a bit by not rolling the sharing view back in time, but instead have the item- importing code check the repository history to detect conflicts. The sharing framework will try and make that job as easy as possible for the implementors of the various "importProcess( )" methods by passing in a data structure describing all local changes during the relevant time period.
~morgen _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
