Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • As a slightly stronger example, the bank can offer variable overdraft limits on their accounts, without having to tell the client side what the limit is on each account. Commented Feb 9, 2015 at 9:30
  • Correct you can make the decision of balance limits as complex as you want and still don't have to make changes to the client. If you take this further with REST parts like content type you can show different views. For example an account looks different from a transaction. Also interesting is code on demand (though not much implemented). That could be used for example for a borrowing estimator. It can give the interface a simple calculator function so the client only needs to implement the inputs for the calculation. It will stay up-to-date from the back-end. Commented Feb 9, 2015 at 13:38
  • 4
    But usually the customer need to know WHY it can't withdraw, so we still need to send an ENUM or String in separate field to the client with reason. And if we still need this, why not simply send him another boolean field canWithdraw instead of a link to the action? Another advantage is ability to change an action's URL without touching the client. But.. what reason to change the URL? In most cases it also some change in semantic or parameters or request/response shape etc. So we anyway need to change the client. So, I still don't get it - what the point of HATEOAS. Commented Dec 17, 2017 at 16:41