Again inaccurate. HTTP verbs are present in HTTP 2.0. Anyone who has a chance will upgrade their servers to use 2.0. You can use protobufs with REST not restrictions their either. There's bunch of REST usuall things people do which some think are requirement.
It just so happens that HTTP was in doctoral dissertation when REST was described.
Point is using underlying protocol to communicate while REST is architectural style that depends on it so not all would satisfy the need as HTTP did.
You added as of right now which to me indicated that no one or barley anyone is using it. While it's just server/framework upgarde depening on the way of deploying apps and such. There's not code change involved so there's no transition in my head just ops part so to speak. But ok I get different way od expressions
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Again inaccurate. HTTP verbs are present in HTTP 2.0. Anyone who has a chance will upgrade their servers to use 2.0. You can use protobufs with REST not restrictions their either. There's bunch of REST usuall things people do which some think are requirement.
It just so happens that HTTP was in doctoral dissertation when REST was described.
Point is using underlying protocol to communicate while REST is architectural style that depends on it so not all would satisfy the need as HTTP did.
How is me saying that REST usually goes with HTTP/1.1 inaccurate? It is the default and people are still making the transition.
You added as of right now which to me indicated that no one or barley anyone is using it. While it's just server/framework upgarde depening on the way of deploying apps and such. There's not code change involved so there's no transition in my head just ops part so to speak. But ok I get different way od expressions