Click here to Skip to main content
15,888,454 members
Articles / HTTP

Bare HTTP is Not Fully RESTful - A Deeper Look at REST Architectural Style and How HTTP Shows Protocol Deficiencies

Rate me:
Please Sign up or sign in to vote.
5.00/5 (3 votes)
4 Mar 2020CPOL4 min read 17.4K   6  
The article tries to map a deeper, more generic nature of REST architectural style into HTTP to show protocol deficiencies.
Here I'll try to map this concept into the HTTP 1.1 protocol (though it applies to HTTP/2 as well) to show that bare HTTP is not suitable to fully host RESTful communication. To illustrate my way of thinking, I'll use an extended music player example from the previous article. I will associate every song with a number of playlist names it can be referenced by to bulk up representations.

Views

Daily Counts

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect
Poland Poland
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions