Re:So you want to offer a public API …
by BerislavLopac on Wednesday July 25, 2012 @07:48AM
(#4290407)
Actually, the difference between XMP-RPC and REST is not just in the format of the response, the difference is the whole approach. The way you have described (didn't go into the docs) you don't have REST at all, just XML-RPC that returns JSON. Sorry if I misunderstood.
[ Parent
| on HN ]
There are two different interfaces for the same implementation. Let me stress the different part. The RESTful API uses JSON to encode the responses, but that's all.
Sorry if I didn't explain it very well, the docs are clearer though.
Re:So you want to offer a public API …
by icebraining on Wednesday July 25, 2012 @08:26AM
(#4290537)
The point is that your RESTful API is not RESTful at all. It's just RPC using JSON. REST is an architectural style that models the interaction around data and hypertext instead of actions.
A good rule of thumb is: if the documentation mentions "methods" as anything other than the uniform ones (if you're using HTTP, that would be GET, POST, etc), then it's RPC, not REST.
Note: I'm not saying your API is bad; RPC is a completely valid model. I'm just saying it's not RESTful.
That's true, we don't use HTTP methods (PUT, GET, POST, DELETE, etc) as part of the API. In fact we treat POST/GET the same for ease of use.
EDIT: to be fair, in the docs we never say it's a RESTFul API, it was MY mistake in my first comment.