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.
Alternatives
Members may post updates or alternatives to this current article in order to show different
approaches or add new features.
No alternatives have been posted.
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.