Web Apis - Restful

Suddenly, a new client—a mobile app—asked REST for the same item. Because REST was stateless, the server didn't have to manage sessions or cookies, allowing REST to handle thousands of requests seamlessly without getting overwhelmed.

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. RESTful Web APIs

Every request contained everything necessary to understand it: the target ( /products/101 ) and the intent ( GET ). The Resource Suddenly, a new client—a mobile app—asked REST for

UserInterface sent a message out across the web highway: GET /products/101 The Journey REST picked up this request

REST was sleek, efficient, and—most importantly—perfectly . The Request

{ "id": 101, "name": "SuperWidget", "price": 29.99, "status": "in-stock" } Use code with caution. Copied to clipboard


934