[cosmo-dev] Ticket management API (Was: Generating tickets to
travis at osafoundation.org
Tue Mar 4 09:45:00 PST 2008
> 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.
+1 on 1), though I think it might make sense to add this stuff to the
Atom API. Certainly CMP isn't the right place, as it has no concept of
collections. Morse code could work, but we'd probably need to double
up and do something in Atom for the web ui.
I just looked again and it turns out ticket discovery is already
available via the Atom collection details projection. (http://chandlerproject.org/Projects/CosmoFeedCollectionsAndItems#Details
Ticket creation could be handled a number of different ways. One
possibility is to handle it the same way we handle collection
modifications today, with some kind of microformat PUT to the
collection url. (http://chandlerproject.org/Projects/CosmoFeedCollections#Modifying%20a%20Collection
Another possibility would be to add some url space to which we could
post Cosmo Atom extension tickets (see details link above). For
example, posting '<cosmo:ticket cosmo:type="read-only">ub33mmsss1</
cosmo:ticket>' to https://hub.chandlerproject.org/atom/collection/d9a6a8a5-7e46-4e7d-94b9-3f20c818e58c/tickets
would create a new read-only ticket on that collection.
Not quite sure what 2 entails, but I get the feeling it only effects
the desktop client story, so I'm +0 for 0.13 if the appropriate
parties want it in :)
More information about the cosmo-dev