Timeline for answer to What's the point with HATEOAS on the client-side? by Davin Tryon
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2019 at 11:53 | comment | added | Davin Tryon | yes, you still have backwards compatibility concerns. This can be solved by including a version header or version in the url. But, I would say you are understanding correctly. | |
| Jan 25, 2019 at 11:32 | comment | added | Myk |
@DavinTryon Thanks for the response. So, for example, given this link "first": { "href": "http://example.com/api/book/catalog" } 1) if href's value changes, the existing [properly designed] clients keep working but 2) if the link's name changes from first to begin, it will break the existing clients. Would you say my understanding is correct?
|
|
| Jan 25, 2019 at 11:11 | comment | added | Davin Tryon | @Nik take a look at HAL for an example of how the links are provided in the response. | |
| Jan 25, 2019 at 11:03 | comment | added | Myk | @DavinTryon "As others have mentioned, the ability to change links on the server (and not break clients) is another advantage." -- this is a huge advantage! Could you please give an example of how such a client can be implemented "on top of" dynamic HATEOAS links. | |
| Jan 15, 2018 at 11:50 | comment | added | Jimmy T. | This only applies when the app that uses the API acts like a browser. | |
| Feb 10, 2015 at 13:23 | comment | added | Cormac Mulhall | @user1620696 You should know all of this anyway through both the client and server understating the content type if the resoure. Content type is a lot more than dumb xml or Json. You should have some "bank deposit" content type that the client understand how to work with | |
| Feb 9, 2015 at 22:16 | comment | added | Davin Tryon | Yes, it could. Again it depends on how dynamic that you want to take it. As others have mentioned, the ability to change links on the server (and not break clients) is another advantage. And this becomes very interesting once your API has an iPhone, Android, Windows Phone, Mobile Web and Web clients that all use it (not to mention if your API is published for others to build clients on). | |
| Feb 9, 2015 at 22:12 | comment | added | user1620696 | So when building the UI we still need to know everything that the API offers, and then looking at those links we are able to know the state the information on the server is at? So for instance, the UI knows it's possible to deposit, withdraw, transfer or close (knows the possible rels), then it checks what came back in order to see the state? | |
| Feb 8, 2015 at 23:26 | history | answered | Davin Tryon | CC BY-SA 3.0 |