RESTful Web Services
•Transferir como PPTX, PDF•
2 gostaram•1,130 visualizações
An updated version of my RESTful Web Services talk.
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (16)
Semelhante a RESTful Web Services
Semelhante a RESTful Web Services (20)
Último
Último (20)
RESTful Web Services
- 2. What Are Web Services?
- 4. Two Styles of Web Service
- 5. Service-Oriented Architecture SOAP, XML-RPC, etc.
- 6. Resource-Oriented Architecture REST
- 8. URLs
- 9. HTTP
- 10. HTML
- 11. URLs + HTTP + HTML
- 12. URI + HTTP + HTML
- 13. URI + HTTP + Links
- 14. URI + HTTP + Hypermedia
- 15. Fundamental Web Technologies
- 16. REST means using fundamental web technologies idiomatically as the basis for designing web services.
- 17. Why use REST?
- 18. The Web Was Designed For It
- 19. The Web Was Designed For It (Sort of.)
- 20. Appeal to Authority An appeal to authority or argument by authority is a type of argument in logic consisting on basing the truth value of an assertion on the authority, knowledge, expertise, or position of the person asserting it. –Wikipedia
- 21. Roy T. Fielding, Ph.D. • Co-founder, chairman of the Apache Software Foundation • Co-founder of the Apache HTTP Project • On IETF working groups for HTTP, URI, and HTML • Architectural principal on HTTP working group • First name on HTTP spec • Originator of REST
- 22. Sam Ruby • Board member of the Apache Software Foundation • Co-chair of W3C’s HTML Working Group • Co-creator of the Web Feed Validator • Originator of Atom • Secretary of the IETF’s AtomPub working group • Co-author of “RESTful Web Services”
- 23. Greg Hines • Currently giving a presentation about REST
- 24. Fielding developed REST while writing HTTP 1.1…
- 25. Fielding developed REST while writing HTTP 1.1… What have you done lately?
- 26. Aspects of a RESTful Web Service
- 27. Resources
- 28. Resources A resource can be practically anything. • A blog post • A collection of blog posts • An image • A user • Map coordinates • A bank transaction • Search results
- 29. Representations
- 30. A Kitten
- 31. Some Text Name: Bob Breed: Tabby Fur Length: Medium Fur Color: Gray, Brown, White Age: 8 months Personality: Outgoing, but loves to cuddle.
- 32. A Picture
- 33. A Drawing
- 34. A Haiku My cat is named Bob. I named him after Bob. Bob’s breath smells like cat food.
- 35. A Blog Post
- 36. HTML <!DOCTYPE html> <html lang="en"> <head> <title>Greg's Blog: My First Blog Post</title> </head> <body> <article> <header> <h1>My First Blog Post</h1> <p>By Greg Hines</p> </header> <p>This is my first blog post. Woo.</p> <footer> <p>Posted on February 2, 2012 at 12:18 PM</p> <ul class="tags"> <li><a href="/tags/awesome">awesome</a></li> </ul> <p><a href="/entries/2012/02/my-first-blog-post">permalink</a></p> </footer> </article> </body> </html>
- 37. JSON { "uri": "/entries/2012/02/my-first-blog-post", "title": "My First Blog Post", "author": "/users/greg", "created": 1328728680, "content": "This is my first blog post. Woo.", "tags": [ "/tags/awesome" ] }
- 38. Addressability
- 39. Addressability Every resource has at least one URI; every URI points to a resource. http://example.com/entries/2012/02/restful-web-services http://example.com/tags/awesome http://example.com/
- 41. Interface Uniformity GET POST
- 42. Interface Uniformity GET POST PUT DELETE
- 43. Interface Uniformity GET POST PUT DELETE HEAD OPTIONS
- 44. Interface Uniformity GET POST PUT DELETE HEAD OPTIONS TRACE CONNECT
- 45. Interface Uniformity GET POST PUT DELETE HEAD OPTIONS
- 46. Interface Uniformity GET POST PUT DELETE HEAD OPTIONS PATCH
- 47. Idempotency
- 48. Being able to perform an operation multiple times without changing the result after the initial operation.
- 49. Interface Uniformity GET POST PUT DELETE HEAD OPTIONS
- 50. Status Codes
- 60. Connectedness
- 61. Resources Link to Each Other
- 62. Connectedness <?xml version="1.0" encoding="UTF-8"?> <resource xmlns="http://example.com/ns/resource"> <content>...</content> <nextResource href="http://example.com/resource/3"/> <prevResource href="http://example.com/resource/1"/> </resource>
- 63. Connectedness <?xml version="1.0" encoding="UTF-8"?> <resource xmlns="http://example.com/ns/resource"> <content>...</content> <nextResource href="http://example.com/resource/3"/> <prevResource href="http://example.com/resource/1"/> </resource> <link rel="alternate" type="application/atom+xml" href="http://example.com/resource/2.atom" />
- 64. HATEOAS
- 65. Statelessness
- 67. Every Request Happens in Isolation
- 68. State Machine
- 69. Resource State Server-Side
- 70. Application State Client-Side
- 72. Every HTTP request transfers state between the application and the requested resource.
- 73. Resource Application e.g. GET
- 74. Resource Application e.g. PUT
- 76. Representation State Transfer I see what you did there…
- 78. Plain Old XML Level Zero
- 79. Resources Level One
- 80. HTTP Verbs Level Two
- 81. Hypermedia Level Three
- 82. Strive for Level Three
- 83. Be OK with Level Two
- 84. Be Embarrassed by Level One
- 85. Die in a Fire for Level Zero