Future standard GUI library
Roy Smith
roy at panix.com
Sun May 26 14:16:02 EDT 2013
In article <20130526194310.9cdb1be80b42c7fdf0ba502f at gmx.net>,
Wolfgang Keller <feliphil at gmx.net> wrote:
> HTTP will never be a suitable transport layer for a RPC protocol.
What, in particular, is wrong with HTTP for doing RPC? RPC is pretty
straight-forward. Take this method, run it over there, with these
arguments, and give me back the result. HTTP handles that just fine,
with your choice of XML, JSON, or whatever turns you on for the content
encoding.
There are protocols that are more efficient (mostly binary ones like
Thrift and Protocol Buffers), but for a lot of things, the simplicity
and convenience of HTTP is worth than the efficiency hit. It's really
nice to be able to slap together HTTP components like load balancers and
caches by just editing a few config files.
More information about the Python-list
mailing list