3 ms·

All of the things in that post use HTTP. (Though SOAP doesn't require HTTP). Did you mean REST? Even then, people often don't get it right, and it's still not a

• thereason 14y ago
  I meant plain HTTP without another layer of complexity on top. REST to me is someone's PhD thesis, the man who designed HTTP. When I read it, I interpreted it as an argument for the use of HTTP (his baby) and the benefit of keeping things as simple as they can be kept. But lots of people seem to have taken it to be some sort of API. I'm not sure anyone can definitively say what is and what is not "REST", except Fielding himself. All I see is disagreement. I'm in favor of simplification (or more specifically, not adding complexity where it is not needed). Whether that is "REST" or whatever, I don't know. Using just HTTP is simpler. It worked fine before these other things like XML, SOAP and JSON came along. (And I have a hunch that's why he wrote a thesis to illustrate how HTTP can be used for most things people are trying to do with XML, SOAP and JSON.) That's all I know.