REST and the Hypermedia Constraint
•Als KEY, PDF herunterladen•
4 gefällt mir•2,394 views
The document discusses the constraints of REST (REpresentational State Transfer) architectural style. It defines REST as a set of constraints for distributed hypermedia systems. The key constraints are that systems be stateless, cacheable, have a uniform interface, and include hypertext driving application state. The hypermedia constraint requires that hyperlinks define valid state transitions and drive the API, making it RESTful. The document provides examples of how to implement the hypermedia constraint using formats like HTML, Atom, and custom MIME types.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie REST and the Hypermedia Constraint
Ähnlich wie REST and the Hypermedia Constraint (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
REST and the Hypermedia Constraint
- 1. REST and the Hypermedia Constraint
- 3. @blongden
- 9. @ibuildings
- 11. @fdrop
- 13. Hands up!
- 15. REST “Series of constraints for distributed hypermedia systems” Roy Fielding, 2000
- 17. Constraints are good They (help) stop you doing crazy things
- 19. REST is an Architecture It is not a protocol
- 20. Goals • Scalability • Generality of Interfaces • Independent deployment of components • Intermediaries to reduce latency, enforce security, and encapsulate legacy systems.
- 21. Client server
- 22. Stateless
- 23. Cache
- 24. Layered system
- 25. Code on demand
- 27. Uniform interface Identification of resources
- 28. Uniform interface Manipulations of resources through representations
- 29. Uniform interface Self descriptive messages
- 30. Uniform interface Hypertext as the engine of application state
- 31. “What needs to be done to make the REST architectural style clear on the notion that hypertext is a constraint? In other words, if the engine of application state (and hence the API) is not being driven by hypertext, then it cannot be RESTful and cannot be a REST API. Period.” Roy Fielding
- 32. The hypermedia constraint
- 33. The hypermedia constraint A URI request returns all valid state changes
- 34. The hypermedia constraint It’s how the web works
- 35. The hypermedia constraint You already understand it!
- 36. The hypermedia constraint The client tells the server what language it speaks
- 37. The hypermedia constraint The server tells the client what to do
- 38. Hypermedia Types “Hypermedia Types are MIME media types that contain native hyper-linking semantics that induce application flow.” Mike Amundsen (2010)
- 39. HTTP
- 40. HTTP Your browser speaks the language of text/html
- 41. <!DOCTYPE html>
- 42. HTTP/1.1
- 43. HTTP/1.1 HEAD GET POST PUT DELETE TRACE OPTIONS CONNECT PATCH
- 44. GET and POST is OK
- 45. GET and POST is OK REST doesn’t care what methods you use
- 46. GET and POST is OK HTTP cares that the methods are used correctly
- 47. Life in XHTML The website is also the API
- 48. Life in XHTML Inconvenient and difficult to maintain
- 49. False start #1 Attempt a custom hypermedia type
- 50. False start #2 application/atom+xml
- 51. False start #3 application/xhtml+xml
- 52. Custom hypermedia types Consider registered types first
- 53. Custom hypermedia types More likely to be understood
- 55. A solution XHTML has hypermedia controls built in
- 56. A solution Contains most of what I need
- 57. Let’s see it then! @RESTConsole
- 58. XML it’s really good for this stuff
- 59. What about JSON? application/vnd.collection+json application/hal+json
- 60. Versioning http://www.w3.org/History/19921103-hypertext/ hypertext/WWW/TheProject.html
- 61. Versioning The server makes no assumptions on the capabilities of the client
- 62. Versioning If the client does not support something, it simply ignores it
- 63. Versioning The web is not versioned
- 64. Versioning Correct use of hypermedia means you can change things without affecting clients
- 65. Versioning But if you must...
- 66. Versioning Accept: application/vnd.fdrop.xhtml+xml Accept: application/vnd.fdrop.v2.xhtml+xml
- 69. https://joind.in/6326 @blongden
Hinweis der Redaktion
- \n
- Developer for 20 years (started young)\nProfessional developer since 2002\nStarted on C, C++ and Perl\nFocussed on Perl and moved into web app development where I picked up PHP\nNow interested in the mobile web, standards and software architectures\n
- \n
- \n
- \n
- Technical Assurance Manager since the start of 2010\nOne of the Sheffield office founders\n
- Sole developer of fdrop.it\nCreated to solve my problem of &#x2018;why is it so difficult to send a file to someone online?&#x2019;\n
- \n
- Who knows what Rest is?\nKeep your hand up if you know what Hypermedia is.\n
- \n
- one of the principle author of HTTP specification (RFC 2616)\nIn 1999 he was named my MIT Technology Review as one of the top 100 innovators in the world under 35\n\n&#x2018;Architectural Styles and the Design of Network-based Software Architectures&#x2019;\n
- \n
- Constraints help to guide the creative project\n\nSacrifice is usually made retroactively\n
- Can be applied to ANY distributed system\nWeb application or API design\n
- \n
- Clients not concerned about data storage\nServers not concerned about the user interface or user state\ncomponents evolve independently if interface remains constant\n
- Each request from the client must contain ALL of the information required\nCannot rely on stored context on the server\nSession state on the client\nVisibility (Server can be observed at any time)\nReliability (network failure)\nScalability (easy to add servers)\n
- Responses must implicitly or explicitly define themselves as cacheable or not\nFurther improves scalability and performance\n
- Client connected to the end server or to an intermediary along the way.\nLoad Balancers\nSecurity Policies at a Firewall\nReverse Proxy Cache\n
- Service can temporarily extend client side functionality by providing code it can execute \nie, Javascript or java applets\n\nTHE OPTIONAL CONSTRAINT!\n
- Information is transferred in a standardised form.\nFour guiding principles to simplify architecture\n
- On the web we use URI&#x2019;s\n\nResources themselves are usually different to what is returned to the client\nUsually, a database resource will be represented in JSON or XML\n
- Each resource can have one or more representations.\nClients negotiate (con-neg) to agree on format.\n
- Requests contain data and additional headers on how it should be handled\nEach message describes itself. This means using an explicit mime type, and explicitly if the resource can be cached.\n
- Clients make state transitions ONLY through links returned within the resource (ie, anchors in html)\nOnly exception is the entry point\n
- \n
- \n
- \n
- and it&#x2019;s why it&#x2019;s been so successful over the last 20 years. The web is 20 years old. That&#x2019;s amazing - and because of standards and hypermedia, I can still reference things from 20 years ago.\n
- A web page contains all the information within it to allow the user to move from the current state, to the next.\n
- \n
- content negotiation\n
- HTML is a hypermedia type\nXML is not\n
- All types of HTML\nXHTML\n\nVersions within them are identified by the content (DOCTYPE, html tag or xml header)\nXML documents not processed as XML (no checks for well formedness)\n \n
- This is how you declare an html 5 document. It&#x2019;s great for the web as browsers only need to understand GET and POST - this is fine and it&#x2019;s still RESTful, but what if we need a representation of a resource that can support other actions?\n
- \nHTTP 1.1 defines these 9 methods. HTML lets us use 2 of them. \n
- That&#x2019;s all you get in a browser\n\n
- \n
- GET to retrive, POST to create, PUT to update, DELETE\nPOST to a job queue to update and delete\nThese are HTTP, not REST (REST just defines the uniform interface)\n
- \n
- Focus on the UI breaks the API\n
- Craft my own XML doc\nNeed to define my media type first\nToo much like work...\n
- There was merit to this - which i&#x2019;ll come back to\n
- Remove the markup from the XHTML that was only there to layout the UI\nServe HTML5 to browsers on text/html!\nClose - but webkit on iOS and Android devices prefer XML\n
- \n
- \n
- XHTML still in the media type so still self describing\nWont conflict with browsers\n\n
- \n\n
- form, input, img, a\nBrowsers already understand XHTML\nEasy for people to consume using any XML Reader\nDEMO\n
- \n
- Namespaces\nAttributes and values\n\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n