Download as PDF, PPTX
![Determine the request method $_SERVER['REQUEST_METHOD']](https://image.slidesharecdn.com/building-restful-applications-using-php-091031121039-phpapp01/75/Building-Restful-Applications-Using-Php-24-2048.jpg)
![Use Apache's mod_rewrite to make URLs pretty Other web servers offer similar functionality $_SERVER['REQUEST_URI']](https://image.slidesharecdn.com/building-restful-applications-using-php-091031121039-phpapp01/75/Building-Restful-Applications-Using-Php-26-2048.jpg)
Uploaded bySudheer Satyanarayana
Building Restful Applications Using Php
This document summarizes a presentation about building RESTful applications using PHP. REST (Representational State Transfer) is a software architectural style that uses HTTP verbs to manipulate resources. The presentation covers the six constraints that define REST - client-server separation, statelessness, cacheability, uniform interface, layered system, and code on demand. It provides tips for implementing REST in PHP like using the header() function, determining the request method, and encoding/decoding JSON. Questions from the audience are answered at the end.
Building Restful Applications Using Php
- 1. Bangalore PHP UserGroup – 31 October 2009 Building RESTful Applications Using PHP Sudheer Satyanarayana http://techchorus.net http://binaryvibes.co.in
- 2. About Your Presenter Director,Binary Vibes Information Technologies Pvt. Ltd (http://binaryvibes.co.in) Free and open source software supporter PHP programmer Blogger - http://techchorus.net
- 3. Topics What is REST? WhyREST? How to use REST?
- 4. What Is REST? RepresentationalState Transfer Style of software architecture Introduced by Roy Fielding
- 5. Six Constraints DescribeThe Architectural Style Client Server Statelessness Cacheable Uniform interface Layered system Code on demand
- 6. Constraint 1: SeparationOf Clients And Servers
- 7. Clients Browser PHP/Python/Perl/Whatever script Desktop application Commandline Anything that can make an HTTP request
- 8. Advantages Of SeparationOf Clients And Servers Portability: clients are not bothered about data storage Scalibility: servers are not bothered about user interface Independent development of clients and servers
- 9. Constraint 2: Statelessness HTTP is stateless Server does not store client context Clients may hold context Each request contains all information required to process the request
- 10. Advantages Of Statelessness Serversare more scalable Servers are more reliable Servers are more visible for monitoring
- 11. Constraint 3 :Cacheable Responses indicate whether they are cacheable Eliminates some client server interactions
- 12.
- 13. Constraint 4: UniformInterface REST is defined by four interface constraints Identification of resources Manipulation of resources through representations Self descriptive messages Hypermedia as the engine of application state
- 14. Identification Of Resources Resourcecan be anything Article Comment Contact User Employee URI – Uniform Resource Identifier http://example.com/article/1 http://example.com/comment http://example.com/article?title=abc
- 15. Manipulation Of ResrourcesThrough Representations Use the HTTP verbs GET – retrieve one or a collection of articles POST – create a resource PUT – modify an article DELETE – delete an article http://example.com/article GET Return collection of articles http://example.com/article/1 GET Return article whose id is 1 http://example.com/article POST Create an article http://example.com/article/1 PUT Modify the article whose id is 1 http://example.com/article/1 DELETE Delete the article whose id is 1
- 16. Self Descriptive Messages HTTPHeaders HTTP Response Codes 1XX Informational 2XX Success 200 Ok 201 Created 202 Accepted 204 No Content 3XX Redirection 4XX Client Error 403 Forbidden 404 Not Found 5XX Server Error
- 17. Hypermedia As TheEngine Of Application State Provide sufficient information to access related resources When http://example.com/article/1 is accessed Inform the client how to access the comments of article 1 Mention http://example.com/comments?criteria=byarticle&articleid=1 in the response
- 18. Constraint 5 :Layered System Proxies, gateways and other intermediaries Encapsulate legacy services Protect new services from legacy clients Load balancing High performance
- 19. Constraint 6: CodeOn Demand (Optional) Client downloads code from server and executes it Common example: Server generating JavaScript code
- 20. If your systemconforms to these constraints it can be called RESTful
- 21.
- 22. Tips to putthese concepts into practice
- 23. PHP header() function Useheader() function to describe the response headers header("HTTP/1.0 404 Not Found"); header(”Location: http://example.com/movedhere”); header('Content-type: application/xml); header('Content-type: application/json);
- 24. Determine the requestmethod $_SERVER['REQUEST_METHOD']
- 25. Use cUrl fromthe CLI to test REST server Write a PHP script to make HTTP requests PHP supports curl, use the PHP curl_* functions Streams and sockets functions are also available Telnet also works
- 26. Use Apache's mod_rewriteto make URLs pretty Other web servers offer similar functionality $_SERVER['REQUEST_URI']
- 27. Encode data toand decode from JSON json_encode() json_decode()
- 28. Authentication HTTP Authentication API Keyin HTTP header apache_request_headers() $_SERVER
- 29. Your favourite PHPframework might have a component to help develop RESTful servers Use it
- 30.
- 31. Contact me http://twitter.com/bngsudheer http://techchorus.net IRC, Bonaparteon freenode.net Thank you
- 32. Copyright Notice This presentationis licensed under the Creative Commons Attribution- Noncommercial-Share Alike 2.5 India http://creativecommons.org/licenses/by-nc-sa/2.5/in/