On 9/18/07, Mimi Yin <[EMAIL PROTECTED]> wrote: > Why are there all these different ways to subscribe to the same collection?
to my eyes there are only two: one that makes you log in with a username and password, and one that doesn't. tho admittedly there are flavors of the one that doesn't which have different permissions. > The 'ticket' versus 'mc' URL expose something to the user that the web and > desktop clients should probably handle *for* the user. that's certainly true. both of those clients could say something like this: "here's a url that you can use to subscribe to your collection in chandler desktop. when you use it, you'll have to enter your username and password. this lets us keep better track of who's making changes to your items. "if you don't want to have to enter your username and password, or if you want to give your friends a url they can use to subscribe to your collection without having to log in, well here's the one you need to give them read-only access, and here's the one you need to give them read-write." the reason the web ui can't do the second part of that now is that it doesn't have any particular knowledge of any specific tickets. it can list all of the tickets on the item, and if there's only one read-only and/or one read-write ticket, it can just pick those. but what if there are more than one of each? which ones are the ones that chandler created when you published the collection originally? what if there are none? can the ui just pick two and use them? does it matter if those are the ones created by chandler or if they were created by some other application? we might be able to solve that problem by re-defining how we think of tickets. instead of allowing an arbitrary number of tickets to be issued for a collection, maybe we should only allow one of each type and have them automatically created when the collection is created. that way, assuming you're the person who published the collection, whenever you use desktop or web you can always ask the server to see the single read-only ticket for the collection and you can reliably construct a single sharing (/pim) url to give to others or to use yourself to subscribe in another desktop instance. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
