> This relegates HTTP to nothing more than a transport protocol. Well maybe because it is a transport protocol, it stands for: Hypertext Transfer Protocol HTT

> This relegates HTTP to nothing more than a transport protocol. Well maybe because it is a transport protocol, it stands for: Hypertext Transfer Protocol HTTP is a way to send a message from point A to point B. If your API is tied to HTTP, then you'll have a hard time reusing the same code for another transport protocol, like websockets. Sometimes it makes a lot of sense to use HTTP headers codes for error handling, sometimes it just doesn't work, you can't shoehorn HTTP/REST into everything and expect something good to come out of it.