[E]ach request from client to server must contain all of the information necessary to understand the request, and cannot take advantage of any stored context on the server.
By "stored context" he's referring to application state e.g. what the page number for the next page is vs. resource state e.g. any data store, image etc. - which is arguably the whole point of REST.
Is it fair to say that most attempts at pure rest (hereby defined as an implementation that conforms to the above thesis) must fail due to their reliance on storing session data on the server (persistent or otherwise)?
The concept of a session is common - in particular to Web developers - but is it RESTful according to the above definition?