Page History

...

To be fair, there are plenty of people who appreciate REST in some respects, but ultimately do not see the significance or value of HATEOAS. This approach to RESTful APIs is often referred to as pragmatic REST. RESTful APIs that emphasize HATEOAS is sometimes referred to as purist REST (perhaps derisively by non-purist developers). This article from Ben Morris represents a well reasoned argument against the necessity of HATEOAS, although we suggest that in some ways it indirectly advocates the need to engage HATEOAS. While we agree that HATEOAS is important (and our reasons will be documented below), we believe each developer should Our intent is not to debate the subject or pick apart any arguments against HATEOAS. Rather, we prefer to just outline our case for HATEOAS so each developer can make up their own mind on the matter and . The important part is for a developer to decide early on whether or not HATEOAS will be a normal part of the API or not. This is why the SRP HTTP Framework does not enforce HATEOAS implementation but it does provide tools to make this relatively easy.