Re: [Jersey] What HATEOAS actually means

From: Jan Algermissen <>
Date: Wed, 17 Feb 2010 21:14:13 +0100

On Feb 17, 2010, at 8:26 PM, Mark Derricutt wrote:

> My thought would be that with HATEAOS, any client connecting to the
> system during this work flow would have all the information the need
> returned from the server to participate in that flow, regardless of
> how they joined it.


One property of RESTful applications is that a client can enter the application at any steady state[1] and can understand that state in complete isolation (given it understands the media types of course).

RESTful clients proceed through an application one steady state at a time. They proceed from steady state to steady state by choosing which of the currently available transitions (links) they want to follow (given the overall goal they want to achieve).

[1] Steady state (==application state) is the state reached when all sub requests have been perfomred (e.g. in HTML land the steady state is reached when the Web page and all containing media has been loaded)


> I must download the dissertation again and reread it, but I don't see
> anyone talking about RESOURCE state, only APPLICATION state.

> Any thoughts?
> [1]
> --
> Pull me down under...
>> agreed. Actually I didn't move the posts but changed the team, after
>> learning about the "Link" header from Mr Fielding. ;-)
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

 Jan Algermissen, Consultant
 NORD Software Consulting