[cosmo-dev] Ticket management API (Was: Generating tickets to
randy at osafoundation.org
Tue Mar 4 10:39:21 PST 2008
Grant Baillie wrote:
> 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.
The only way to create tickets now is to:
1. use dav MKTICKET
2. include X-MorseCode-TicketType headers during a mc publish, which
creates the types (if no tickettype headers are present, then no tickets
will be created)
So we could add ticket management support to morse code the feed
service, and with the webui/widgets probably needing the same thing it
makes more sense to add to the feed service.
> 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.
If you don't want the tickets, don't include the X-MorseCode-TicketType
headers in the PUT publish request.
> 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.
I vote for after 0.13 especially if things work now. The client would
still have to do some /pim -> /atom rewriting if we went that direction.
More information about the cosmo-dev