4 ms·
Is it me who does not understand what HATEOAS is? Always thought that it was basically each server generated page providing the list of links/actions that was
by aatd86 3y ago
Is it me who does not understand what HATEOAS is?
Always thought that it was basically each server generated page providing the list of links/actions that was allowed from then on.
Basically a lazy, incremental, and fine grained API.
The issue being that it might not be very useful since links have to persist in general on the web. (maybe I misunderstand and it's a non issue?) whereas HATEOAS would be useful if links were never shared: then they could be dynamically generated or updated?
- mkl95 3y agoHATEOS consists mostly of linking responses ("resources") to each other, as opposed to nesting data. So instead of looking at some nested data, you will follow a link to that data, and so on. You probably won't see it in the wild too often, because RPC rules the world.
- chromanoid 3y agoI think the idea is to provide your API as some part of the consumer internet. The problem is that a bunch of websites tends to be hard to be navigated meaningfully by a machine, since the machine must be able to process the moving parts in way they do not loose meaning. The idea is that you can simply change a link in a result to be able to split your API in an API that is served by multiple endpoints (e.g. microservices) etc.
- aatd86 3y agoOh makes sense... It's like these books in which you are the hero. Depending on the use agent and what not, the routes through a given server-rendered website can be different, tailored, per request.