5 ms·
I actually quite like XML-RPC. SOAP is too complicated for simple services and from everything I've seen REST only defines the URL layout while the format of t
by vsync 16y ago
I actually quite like XML-RPC.
SOAP is too complicated for simple services and from everything I've seen REST only defines the URL layout while the format of the data is up to you. So you end up sending some XML-RPC like thing over the transport.
Then there are issues like GET requests getting arbitrarily limited in size, character encodings, and stuff that makes it not even worth trying to do function calls (even idempotent ones) with anything but POST.
I wish it were otherwise.
- Shaping 16y agoThis is interesting. I like REST for its URL resource name-space idea, but less so for its lack of specificity/standards for choosing media types and doing security. Concerning the GET limitations specifically, what problems were you having with size and character encodings? This makes me think that the REST verb-structure-as-hyper-media-CRUD model is broken from the start, in terms of scalability.
- vsync 16y agoI believe URLs are limited to 1000 or 1024 bytes, or are in practice on some browsers (probably IE of course), and are either limited to 7-bit ASCII for strict compliance or the character encoding is just undefined. It's been a while since I looked at the RFCs in detail on this and I'm sick right now so I apologize for the lack of detail.