On 9/18/07, Mimi Yin <[EMAIL PROTECTED]> wrote: > Oy, there are 4 URLs?
Well, there are an infinite number of URLs. I just brought up the four flavors which seemed most appropriate to discuss. :-) The user should never see /mc/ URLs IMHO. > I was mostly talking about 1) and 4). > > Redirecting 1) to 4) *IF* there is account info available. 1) http://server/pim/collection/<uuid>?ticket=<ticket> So there are three scenarios with this one: A) Chandler subscriber has no server account B) Chandler subscriber has a server account, and is the publisher of this collection C) Chandler subscriber has a server account, but is not the publisher of this collection A) is straightforward, they have to use the ticket's rights However, in B) and C) Chandler doesn't know beforehand whether the collection was published using one of the subscriber's accounts, or by someone else; this would require additional handshaking with Cosmo to get the list of published collections, etc. Ok, I could do that, but within B), there are two subcases: B1) ticket is read-write B2) ticket is read-only In B2), do you want the user to end up being able to write to the subscribed collection? That might be counter-intuitive to subscribe with a read-only ticket and end up with write privileges. I'm suggesting that in A), B), and C), the Chandler subscriber simply gets the ticket's rights, unless you feel strongly that you want to change this current behavior. ~morgen _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
