3 ms·

I think the whole point the article is trying to make is that REST isn't really a step forward from RPC. It just adds an overly restrictive taxonomy (i.e. in a

I think the whole point the article is trying to make is that REST isn't really a step forward from RPC. It just adds an overly restrictive taxonomy (i.e. in a complex practical application, you're probably going to run into a problem that doesn't fit the REST model well), and doesn't actually solve any real problems.

dragonwriter 12y ago
That may be the point of the article, but neither it nor any of the other instance of people making similar claims I've seen supports it convincingly.
lmorchard 12y ago
REST doesn't add "restrictions". REST describes constraints that - if you can work within them - provide certain guarantees and benefits and capabilities. It solves a bunch of real problems. REST wasn't just pulled out of thin air - it was an attempt to describe how the web itself works at global scale.