[Cosmo-dev] Cosmo and Scooby URLs

[Brian Moseley]

On 6/16/06, John Townsend <johntownsend at mac.com> wrote:

> the urls could be something like:
>
> http://cosmo-demo.osafoundation.org/sharing/<username>/<calendarName>
> [?ticket=<ticketID>]
>
> 1. The default behavior would be to just to Scooby.
> 2. If accept headers are present, then the request could be forwarded
> onto to Cosmo.
> 3. For clients that can't set the accept headers, we can add request
> parameters:
>      - ...&render=WebDAV|CalDAV|Atom|WebApp, etc.
> 4. The ticket part is optional. If you don't specify the ticket, then
> it just attempts to go to that user's calendar collection.

this does not solve the problem of using the same url for browsers and
non-browser clients. without a header, query parameter or some other
token, there is no way for cosmo to know to redirect firefox to scooby
but to send an icalendar response to ical.

this discussion raises an interesting question: if it really is the
ecosystem, stupid, why don't we just combine scooby, cosmo and osafsrv
into one app?

pros:

1) we could improve the performance of scooby by accessing the
repository locally rather than over caldav
2) there would be no "cleanliness" issue with having cosmo redirecting to scooby

cons:

1) we'd still have the potential problem of having multiple possible
responses to a single unparameterized url, depending on the
capabilities of the requesting client
2) it might feel unnatural for those who just want a protocol server
to also get a calendar ui, and vice versa (altho we could provide
configuration options to turn each of those features on and off)