On RESTful API Standards – Just Be Cool: 11 Rules for Practical API Development

Re:On RESTful API Standards – Just Be Cool: 11 Rules for Pra... by DropkickM16 on Tuesday May 01, 2012 @11:37AM (#3914843)

I don't think adding metadata to your responses goes against the ideas of HATEOAS. On the contrary, HATEOAS requires enough metadata about the application state and possible transitions so that a consumer can fully interact with the API without relying on out-of-band information (URL patterns being the most common example).

[ Parent | on HN ]

Re:On RESTful API Standards – Just Be Cool: 11 Rules for Pra... by thelarry on Tuesday May 01, 2012 @12:10PM (#3915017)

Some people argue that whatever you get back from the request should be the exact json/xml/whatever object representation.

[ Parent | on HN ]

Re:On RESTful API Standards – Just Be Cool: 11 Rules for Pra... by DropkickM16 on Tuesday May 01, 2012 @12:32PM (#3915139)

Can you point me to a source for this argument? I'd be interested in taking a look at the reasoning behind it. Obviously, that's an approach that a lot of people take for pragmatic reasons, but it doesn't seem to allow the kind of hyperlinking that's the core idea of HATEOAS. Of course, the term "object representation" is pretty generic, and may obviously somehow include links to related resources and application states.

[ Parent | on HN ]

Re:On RESTful API Standards – Just Be Cool: 11 Rules for Pra... by rfugger on Tuesday May 01, 2012 @02:09PM (#3915644)

I doubt Fielding would agree:

"The model application is therefore an engine that moves from one state to the next by examining and choosing from among the alternative state transitions in the current set of representations."

http://weblogs.java.net/blog/mkarg/archive/2010/02/14/what-h...

[ Parent | on HN ]