[Cosmo-dev] JSON-RPC considered harmful

[Mikeal Rogers]

>> It may seem like what is being proposed is a whole new protocol, and
>> perhaps in some ways it is, but it's really a taking a bunch of
>> pieces that already exist in Cosmo (JSON serialized objects, ticket
>> processing code, Cosmo UI RPC methods, RESTful Http protocols) and
>> putting them together in a new way.
>
> it would still be a bunch of code to write, and we don't have all that
> much time left. doing this the right way, with gdata or calatom, will
> take more time than we've got. i'm all for doing it eventually,
> hopefully for preview even, but not just now.
>
> as i told travis in irc earlier, i was envisioning simple anonymous
> json-rpc access to a separate url with just the methods needed for
> anonymous calendar viewing. all of these method signatures would
> include a ticket key and would do manual ticket authentication.

That's what I was thinking.

It would be nice if we had unified across all the interfaces.  
Currently the other interfaces use basic auth or ?ticket=hash, and  
the url is a reference to the calendar collection, but the json-rpc  
interface uses sessions and sends requests to a single path.

The only problem with this is that it would exclude the use of json- 
rpc GET requests since the ticket param would conflict.

-Mikeal