Even doing something like /RPC?method=add is more RESTful than what JSON-RPC is doing.

OHM is a library I wrote to make exposing a single object easier: http://pythonpaste.org/ohm/

Your json-rpc example is very appreciated. But you state “In fact I don’t like JSON-RPC. It’s unnecessarily un-RESTful, and modelled too closely on XML-RPC.”

Can we get an example that is restful?

Thanks

There’s an example in the last section, but that’s very far down; someone skipping through the library reference won’t read down that far. BaseHTTPServer’s docs, on the other hand, have an example in the opening section.

As to equivalents: wsgiref.simple_server is really the equivalent to BaseHTTPServer. You could write this without using WebOb, and I think it would still be simpler. BaseHTTPServer kind of has a weird little framework in it, which confuses things a bit — but that’s part of why you should use WSGI, where these different things are not confused. With WSGI, servers serve, and they don’t do anything else. They don’t dispatch, they don’t look at the request method, they don’t do any of that.

“I don’t know why people keep writing these”

As someone recently guilty of writing a new RESTful “microapp” using BaseHTTPServer, some reasons;

• a: Don’t have the big picture yet of all that wsgi means to me as someone wishing write RESTful microapps (vs. e.g. someone writing frameworks)
• b: Seen in a certain light, wsgi represents have choices and making decisions – a paradox of choice thing
• c: BaseHTTPServer has the advantage of batteries included
• d: Red Hat only recently bumped up to python 2.4…
• e: I was aware of my sin ( but lacked time to figure out how not to be a sinner

If you still have some drive to write on this topic, in particular, for point b, some kind of decision tree would really help. E.g. WebOb – is that the recommended “equivalent” to BaseHTTPServer?