| I think you're mixing up multiple things. - HTTP is a protocol. - HTML is a markup lanaguage. - REST is an architectural model for building web services. They are all different. > HTTP is not a programming language..
> HTTP statuses
> REST is stateless HTTP is a protocol. A protocol by definition allows certain constructs and prohibits others. There are books available for modeling real-world problems with REST, such as RESTful web services cookbook. I'd suggest going through them, before declaring REST is impractical. >I'm not sure if I can do it pragmatically in HTTP without getting yelled at You can certainly use HTTP as you like it, just please don't call it RESTful unless it actually is. A lot of web APIs are not RESTful, nothing wrong with that. > don't tell me HTTP is the best we can do.. Unfortunately it is for now. Everybody is free to invent their own protocol, write production quality servers to implement it, and get everybody else to adopt it. |