If I am going to clean this up, what should I use for the jsonrpc part (I am assuming this is used by the cgi + mod_python scripts)? I have been using jsonrpclib (https://github.com/joshmarshall/jsonrpclib/), but I found an annoyance, the request params value is always an array. Yes, even if it is an array that contains one dictionary. I see no reason for this as the specs for the proposed JSON-RPC 2.0 allow it to be a structured value (at this time think python array or python dict).
Anyhow, jsonrpclib is basically subclassing xmlrpclib and substituting json writing/parsing for xml writing/parsing. Personally, I yajl for my server side stuff (Python and C), jsonrpclib to test the server, and javascript XHR to send the request via browser. (although yajl has a annoying dependency chain -- I forget what exactly -- like git + ruby or ....). Also, what about chucking mod_python and using mod_wsgi for the example code? I don't recommend using mod_python. Also, for Mac OS X the mod_wsgi and newer fast cgi modules are already included. I don't know about apache for windows or linux distributions other than gentoo. Also, given the issues i've seen with mod_python and very infrequently with mod_wsgi, I would recommend not running python code inside apache (as mod_python does, and mod_wsgi can be configured to do so). This may have something to do with my loading massive boost::python extension modules into a mod_wsgi interpreter :) --Jeff
