This was a , a standard HTTP method meant for retrieving data. REST picked up this request. REST didn't care that UserInterface had asked for Product #99 just a second ago. REST didn't know who UserInterface was, and didn't need to know.
Every request contained everything necessary to understand it: the target ( /products/101 ) and the intent ( GET ). The Resource RESTful Web APIs
Explain the concepts of (Hypermedia as the Engine of Application State) in a story format What aspect of RESTful APIs This was a , a standard HTTP method
{ "id": 101, "name": "SuperWidget", "price": 29.99, "status": "in-stock" } Use code with caution. Copied to clipboard REST didn't know who UserInterface was, and didn't
Later, UserInterface needed to change the price of the SuperWidget. It sent a new request: PUT /products/101 with the new data.
UserInterface sent a message out across the web highway: GET /products/101 The Journey
One morning, a frontend application known as "UserInterface" needed to know about a specific item in the inventory, Product #101. It didn't want to talk for long, just get the facts.