3 ms·
This seems like the most traditional and respectful of REST way to go. You could try a HATEOAS approach if you want to get a bit more fancy. https://restfulap
by contentboot 4y ago
This seems like the most traditional and respectful of REST way to go.
You could try a HATEOAS approach if you want to get a bit more fancy.
https://restfulapi.net/hateoas/ https://restfulapi.net/hateoas/
If you are following REST strictly there should be only objects, actions and verbs.
- arinlen 4y ago> If you are following REST strictly there should be only objects, actions and verbs. Not quite. That would be a resource-based architectures much like REST, but REST dials requirements a notch higher, with stuff like adding capabiliy-discovering semantics to resources such as navigation links to related resources and operations to express it's state and state-changed, in the form of HATEOAS.