Timeline for answer to How does HTML-based HATEOAS apply in applications which also want to expose an external API? by Bart van Ingen Schenau
Current License: CC BY-SA 4.0
Post Revisions
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 31, 2025 at 23:47 | comment | added | Greg Burghardt | @DMJ, I think you might be missing the concept. HATEOAS doesn't prescribe a data format. It provides automated discoverability of the actions you can perform on a resource. The client (JavaScript or the human) doesn't need to construct the URLs. Humans get links. Programs get a collection of URLs. Same concept in a different form. | |
| Jan 31, 2025 at 15:06 | comment | added | DMJ | While I'm aware that the general principles can apply to a JSON-based payload, I don't necessarily think that the two are well-matched to one another, whereas HTML is well matched to the HATEOAS principles. Sending HTML over the wire rather than JSON was a big part of why it appealed to me, and thus something I don't want to give up in my solution. | |
| Jan 31, 2025 at 7:26 | history | answered | Bart van Ingen Schenau | CC BY-SA 4.0 |