hypermedia_system_revisit_roy_fielding .
0 likes178 views
この資料は、Roy FieldingのREST論文（第5章）を振り返り、現代Webで誤解されがちなRESTの本質を解説しています。特に、ハイパーメディア制御やアプリケーション状態の管理に関する重要なポイントをわかりやすく紹介しています。 This presentation revisits Chapter 5 of Roy Fielding's PhD dissertation on REST, clarifying concepts that are often misunderstood in modern web design—such as hypermedia controls within representations and the role of hypermedia in managing application state.
hypermedia_system_revisit_roy_fielding .
- 1. Hypermedia Systems: Revisiting Roy Fielding’s RESTful Architecture What’s Misunderstood or Ignored in Modern Web
- 2. Background Among popular web application architectures, there seems to be misunderstanding or ignorance on “RESTful” proposed by Roy Fielding’s original dissertation.
- 3. Status Quo of “RESTful” RESTful API Docs
- 4. Misinterpretations in Modern APIs - Many so-called “RESTful” APIs today lack hypermedia controls. - True RESTful systems should provide hypermedia-driven interactions, not just JSON data exchanges .
- 6. Real Constraints of REST Fielding defines “constraints” to describe how a RESTful system behaves: ● It is a client-server architecture (section 5.1.2). ● It must be stateless; (section 5.1.3) that is, every request contains all information necessary to respond to that request. ● It must allow for caching (section 5.1.4). ● It must have a uniform interface (section 5.1.5). ● It is a layered system (section 5.1.6). ● Optionally, it can allow for Code-On-Demand (section 5.1.7), that is, scripting.
- 7. The Uniform Interface Constraint In Section 5.1.5 for the Uniform Interface constraint, Fielding says: The central feature that distinguishes the REST architectural style from other network-based styles is its emphasis on a uniform interface between components… In order to obtain a uniform interface, multiple architectural constraints are needed to guide the behavior of components. REST is defined by four interface constraints: identification of resources; manipulation of resources through representations; self-descriptive messages; and, hypermedia as the engine of application state. Roy Fielding, Architectural Styles and the Design of Network-based Software Architectures
- 8. JSON vs HTML Representation { "name": "Joe Smith", "email": "joe@example.org", "status": "Active" } <html lang="en"> <body> <h1>Joe Smith</h1> <div> <div>Email: joe@example.bar</div> <div>Status: Active</div> </div> <p> <a href="/contacts/42/archive">Archive</a> </p> </body> </html>
- 9. Hypermedia As The Engine of Application State <html lang="en"> <body> <h1>Joe Smith</h1> <div> <div>Email: joe@example.bar</div> <div>Status: Active</div> </div> <p> <a href="/contacts/42/archive">Archive</a> </p> </body> </html> <html lang="en"> <body> <h1>Joe Smith</h1> <div> <div>Email: joe@example.bar</div> <div>Status: Archived</div> </div> <p> <a href="/contacts/42/unarchive">Unarchive</a> </p> </body> </html>
- 10. Hypermedia System In Practice Benefits - Simplified frontend development - Simple architecture Challenges - UI Limitations - Bandwidth