Hacker News Reader

Comment by jbenner-radham | Hacker News Reader

What are you referring to when you say “no link in sight” in regards to REST?

Basically, instead of having a "User" response built like this:

  User {

    name: "Bob"

    id: 1

  }

You would have something like this:

  User {

    name: "Bob"

    href: "http://www.example.com/api/users/1"

  }

This kind of reminds me of hateoas. [1]

Isn’t that HATEOAS and not REST specifically? I don’t remember anything in Roy Fielding’s dissertation specifying any type of response body.

Thank you for your input. I will consider this feature going ahead.

Thank you for that link. I’ve read through Roy’s original dissertation but apparently missed some of the details. This post helps clarify things.

Hypermedia as the Engine of Application State