News for hackers. Stuff that matters.
Re:Nobody Understands REST or HTTP by bad_user on Monday July 04, 2011 @03:19AM (#2725690)
Pagination is implicitly non-restful as page=X can change anytime a new book is added, depending on the ordering getting done.
Re:Nobody Understands REST or HTTP by pornel on Monday July 04, 2011 @07:08AM (#2726174)
Roy Fielding's paper says that "temporal services" are OK:

> A resource is a conceptual mapping to a set of entities, not the entity that corresponds to the mapping at any particular point in time.

http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch...

Re:Nobody Understands REST or HTTP by bradgessler on Monday July 04, 2011 @04:03AM (#2725775)
That's like saying that a resource is implicitly non-restful because its state might change.

If a book is added, the page=x resource is simply outdated and should be refreshed.

Re:Nobody Understands REST or HTTP by justincormack on Monday July 04, 2011 @05:02AM (#2725901)
If you need page stability you can refer to the items at the top of the page not the page numbers, the nice thing about rest is they are still just next and prev links.