On 12/18/07, Randy Letness <[EMAIL PROTECTED]> wrote: > Consider this scenario: > > - User 1 publishes collection A with item aaa > - User 1 gives read-only ticket to User 2 > - User 2 gets item aaa, modifies it and shares it in published > collection B > > User 2 has read only access to aaa in collection A, but write access to > his copy in collection B. User 2 modifies his copy. What happens in > this case? Now there are two copies of aaa that aren't in sync because > one is read-only, but in Chandler its only represented as 1 item right?
Yes, it's one item. Chandler will show the user the item with their local changes, and (obviously) not write those back to the read-only share on the server. If afterwards someone else changes the item in the read-only share, Chandler will show a pending change on the item that the user can choose to apply/discard. The sharing framework allows Chandler to maintain the differences between a local copy of an item and any number of shares. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
