[Cosmo-dev] Display name changes to collections don't sync
morgen at osafoundation.org
Fri Oct 12 10:03:02 PDT 2007
On 10/11/07, Brian Moseley <bcm at osafoundation.org> wrote:
> On 10/11/07, Ted Leung <twl at osafoundation.org> wrote:
> > Bug 11010: <https://bugzilla.osafoundation.org/show_bug.cgi?id=11010>
> > is about syncing collection name changes. There are a few issues here:
> > 1. is there cosmo side work to be done?
> > 2. is there desktop work to be done?
> > 3. do those two piece of work need to release together?
> 1. doesn't appear to be
> 2. yes
> 3. n/a
I don't have a clear picture on what the requirements are. Let's
break it down into the different options:
1) A collection has a single global name and that if anyone changes
it, everyone else sees that new name.
2) A collection has a master name on the server (determined by the
client which originally published it), but each client (including
WebUI) maintains a "local" name for the collection. For example, if I
name my collection "Work", publish it, and you subscribe to it, you
should be able to (locally) rename it to "Morgen's Work" to
distinguish it from your own "Work" collection.
Then there is the question of who gets to rename a collection.
For option 1 there are three subchoices:
1A) Only the publisher gets to rename it
1B) Publisher plus read-write ticket subscribers get to rename it
1C) Publisher plus any subscribers get to rename it
Option 1 doesn't appeal to me, so I'll move onto 2...
For option 2 it's more complicated; you have to make choices about
when to send a name change and when to honor and inbound name change.
I'll just propose the option that makes the most sense to me (others
can give counter proposals):
Anyone can locally change a collection's name but only the owner of
the collection (or perhaps anyone with read-write ticket) is allowed
to update the master name on the server. When the client syncs and
receives an inbound collection name change, the change is applied
locally iff the client hadn't previously renamed the collection. This
means that if I subscribe to your collection and don't rename it, but
you later rename it, I'll see that name change. However, if I have
renamed it (to include your name in the title for example), I will
disregard any future renames you make.
If we go with this proposal, I imagine there would be WebUI work,
which is why I didn't immediately assign this bug to me -- we'll need
to split the bug into two, for Desktop and WebUI.
More information about the cosmo-dev