I'm collecting popular misconceptions about REST. Got some of your own? Please let me know using #notrest. I'll follow up with a few.
28
9
4
@stilkov Not sure what you're looking for but IMO the idea that REST is "better" or "more powerful" than RPC is misguided. #notrest
1
@rolandbouman I don't think it's a misconception that REST is “better” than RPC (depending on what you mean by RPC, of course)
3
@stilkov ...procedure call as a particular resource operation, is far from straightforward. RPC is more general, therefore more powerful.
2
@rolandbouman Understood, and strongly disagreed with. More than will fit in 140 characters.
1
@stilkov I respect it if you don't want to elaborate your reasons on twitter but can you at least provide a link or so to argue your case?
1
Replying to @rolandbouman
@rolandbouman Currently on the road, but maybe this will address some of it: infoq.com/articles/tilkov-re…

Feb 28, 2013 · 4:16 PM UTC

4
Replying to @stilkov
@stilkov So right in the example example.com/calculation?a=2&… I would argue this is simply RPC with a pretty url. You can *think* about it as ...
Replying to @stilkov
@stilkov ...a resource; that doesn't change the fact that it is, in fact, a remote operation addressed through a URI.
Replying to @stilkov
@stilkov (By advocating RPC I am by no means supporting old-skool SOAP. I like JSON for the data exchange, but RPC for the protocol)
Replying to @stilkov
@stilkov At least this example still uses a query. Some ppl take "pretty urls" too far and dream up stuff like myrestservice.com/plus/1/2 -> 3