Pylons and JSON-RPC 2.0

Posted on Jul 13, 2010

I just uploaded some updates to my pylons fork this afternoon. The update is a little radical (as I suspect most projects are in their early stages). Among the changes are:

The error handling is coming along, but leaves something to be desired in my opinion. For one, some of the reserved errors aren’t necessary to export to the controller implementor (“Parse error” comes to mind). There are also a few instances where I’ll need to return better errors such as catching parse errors when decoding the request body. As always, if anyone has any suggestions I am all ears.

Once error handling is pretty and clean I think the next steps will be to look at batch and possibly notifications. I’m not even sure these can be supported on Pylons. Ideas welcome.