[cosmo-dev] Ticket management API (Was: Generating tickets to share collections)

Grant Baillie grant at osafoundation.org
Tue Mar 4 07:53:34 PST 2008


On Feb 14, 2008, at 12:22 PM, Mimi Yin wrote:

> ...
>
> + Don't automatically generate tickets when publishing collections;  
> INSTEAD
> + Replace the [Copy URL(s)] button from both the Publish... and  
> Manage Share... dialogs with an [Invite...] button; WHICH
> - Generates 2 sharing tickets; AND
> - Pops up the Share>>Invite... dialog.

Howdy, y'all

[redirecting to cosmo-dev@; the above text was "Option 2" in a  
chandler-dev@ discussion. See also Chandler Desktop bug 11844]

So, I  implemented the above (mostly) on the client side by using DAV  
for ticket management (i.e. the MKTICKET extension, the  
ticketdiscovery properties, etc). My questions/observations are:

1) The current code, which does a /pim --> /dav URL rewrite, has a  
hacky feel to it, though it works on the hub (and, presumably, an out- 
of-the-box cosmo installation). I checked the online morsecode/cmp  
docs, and didn't find anything regarding ticket management:  
Presumably, at some point it will be added to one of these protocols.

2) Currently, the server automatically creates the tickets when the  
client POSTs the new collection. (I had thought this was optionally  
tweakable by the client, but had misread the code). To implement the  
above, I could just go and remove the newly-created tickets, but it  
would be nice to avoid the extra round-trips.

I'll go ahead and file bugs for these 2 (assuming they don't already  
exist). Do you think either could/should be addressed in 0.13? Both  
client-side workarounds have a crufty feel to them, but we could  
probably live with them for now.

--Grant






More information about the cosmo-dev mailing list