Why Restful
1 like617 views
This document discusses RESTful development and the REST architectural style. It defines REST as having resources that are accessed via HTTP methods like GET, PUT, POST, and DELETE. Resources can be any meaningful concept, and clients initiate requests to servers, which process the requests and return responses transferring representations of resources. The document also outlines the common 3-tier architecture of REST systems with clients, servers, and resources, and provides examples of how HTTP methods map to CRUD operations on resources.
Why Restful
- 1. WHY RESTFUL DEVELOPMENT Representational State Transfer.
- 2. Web services! Web Services can convert your applications into Web-applications. 1. SOAP(Simple Object Access Protocol) / XML-RPC => communication 2. REST => communication + standardisation
- 3. What is REST 1. Everything is a resource 2. REST-style architectures conventionally consist of clients and servers. 3. Clients initiate requests to servers; servers process requests and return appropriate responses. Requests and responses are built around the transfer of representations of resources. 4. A resource can be essentially any coherent and meaningful concept that may be addressed
- 4. Action URL HTTP Method However, the HTTP protocol defines eight methods, GET, POST, PUT, DELETE, HEAD, TRACE, OPTIONS, and CONNECT. REST is concerned with the first four of these methods, GET, POST, PUT, and DELETE. These are the methods that a RESTful web application will use to manipulate resources. ● GET maps to show -> get /teams/:id ● PUT maps to update -> put /teams/:id ● DELETE maps to destroy -> delete /teams/:id ● POST is a bit of an exception, since the resource is not yet existent thus it maps to the base /teams
- 5. The 3 tiered REST architecture