Re: [Jersey] JAX-RS == REST? Or not? (was Re: [Jersey] What HATEOAS actually means)

From: Tatu Saloranta <>
Date: Mon, 22 Feb 2010 09:59:53 -0800

On Sun, Feb 21, 2010 at 1:24 AM, Markus Karg <> wrote:

> Please find inline.
Totally disagree. Still did not receive a single technical argument against
> statelessness, but solely business constraints enforcing storing resources
> on the server side, which is *not* a violation of REST's statelessness.
> Storing a cart on the server's side is *not* violation REST's statelessness
> as it is not stored as part of the conversation state but as part of the
> business concept. What we actually had been talking about was that a cart is
> getting stored on the server side *without* a business need, so *then* it is
> a violation of REST's statelessness.

I agree wrt shopping cart. It is not a good example. I disagree on "only
business reason" part, but I think we are entering a tangential point here,
and something related to our relative length of experience implementing
systems and knowing what all is needed.
No point in getting further there, so I will leave it at that.

As to more important points, I think I get it: resource state (managed by
resource owner) and discussion state (only managed by client) is an
important distinction.
Shopping cart not being a good (enough) use case to help understand bigger
And there being many areas that could be discussed but that go beyond
general focus (and interest).

-+ Tatu +-