[Cosmo-dev] Re: [Design] [Chandler][Cosmo] Cosmo-Chandler Dashboard-Sharing issues

[Bobby Rullo]

ha! I was wondering if we had something like this. We should do  
SOMETHING with this for preview. The hard part again, is the UI.

Bobby

On Feb 9, 2007, at 9:36 AM, Randy Letness wrote:

> Hey Bobby I just thought of something while reading this.  Cosmo ui  
> could utilize the "version" property of items.  This attribute 
> (integer) is updated each time an item is updated.  So, RPCService  
> could detect conflicting updates by comparing the "version" of the  
> item it first read to the "version" of the item that it retrieves  
> before doing the update and if they don't match....throw a conflict  
> exception.  Make sense??  Otherwise RPCService will overwrite  
> conflicting changes.
>
> -Randy
>
> Mimi Yin wrote:
>>
>>
>> However, it seems like the only way a Cosmo user would unwittingly  
>> overwrite a Chandler user's changes is if:
>> 1. Cosmo user goes to view a shared collection.
>> 2. Chandler user syncs change to an item in shared collection.
>> 3. Cosmo user edits the item before their browser has a chance to  
>> refresh to reflect the Chandler user's changes. (I'm assuming  
>> there's no way to push a refresh from the server end if new  
>> changes are detected in a shared collection?)