Hypermedia
Fleeting- External reference: https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
- External reference: https://en.wikipedia.org/wiki/Hypermedia
nonlinear medium of information that includes graphics, audio, video, plain text and hyperlinks.
hypermedia as the engine of application state
- External reference: https://en.wikipedia.org/wiki/HATEOAS
I am getting frustrated by the number of people calling any HTTP-based interface a REST API
— https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
a client interacts with a network application whose application servers provide information dynamically through hypermedia. A REST client needs little to no prior knowledge about how to interact with an application or server beyond a generic understanding of hypermedia.
That is RPC. It screams RPC. There is so much coupling on display that it should be given an X rating.
— https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
, 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
— https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
REST API should not be dependent on any single communication protocol,
— https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven
Notes linking here
- Carson Gross — Return To Hypermedia: Solving Javascript Fatigue Using Fundamental Web Architecture - YouTube
- htmx