Re: the meaning of stateless

Mark Baker wrote:
> 
> If I can say, you seem to be coming from a very solution-driven place,
> where you have a solution in mind and then try to map it back onto
> REST. I would suggest trying the other way; starting only with your
> "business" requirements and moving forward from there, staying within
> the constraints of REST to inform you what a solution might look like.
> 

...

> 
> I think it can be achieved in most cases, and IME, most of the cases
> it *can't* are due to efficiency concerns, not because of any
> conflicting business requirement.  Businesses have been communicating
> (internally and externally) statelessly long before computers came
> around.
> 

/me gives notworthy bow to the REST whisperer...

-Eric