On 10/12/07, Jeffrey Harris <[EMAIL PROTECTED]> wrote: > Moving this to the design list, since I don't think ultimately it's a > Cosmo issue...
... but you left out all of the context of the discussion ;) i think some people are overlooking the fact that, on the server, a subscription is a different entity than the collection itself. the subscription knows: the identity of the subscriber, the uuid of the collection, the ticket used to access the collection, and a name for the subscription that is unique to the subscriber. let's say Jeffrey publishes a collection named "Work". i can subscribe to it and name the subscription "Jeffrey". i can then rename that subscription to "Jeffrey's Work". neither of these subscription naming operations have any impact on the collection's name. if Jeffrey changes the name of the collection to "My Work" (with dav or atom or in the desktop), i'll never notice, because my subscription is based on the collection's uuid, not its name, and because my subscription's name is independent of the collection's name. therefore, the desktop can sync collection name changes without any fear. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
