News for hackers. Stuff that matters.
Re:Nobody Understands REST or HTTP by latch on Sunday February 26, 2012 @07:50AM (#3635508)
He didn't go over the common example of paging by including

   nav { prev: '...', next: '....'}
in the response. But, the thing that always concerns me about this is that it requires the client to maintain state. If you consume such a web service in a web app, and the user hits "next", you'll have to have stored the next url somewhere.
Re:Nobody Understands REST or HTTP by icebraining on Sunday February 26, 2012 @08:16AM (#3635556)
If you want to show any content to the user, you'll always need to hold it in memory somewhere; that's inevitable. Storing an URL for an action is just part of the rest.

Personally, I'd just use a closure and bind it immediately to the event handler of the UI element.

Re:Nobody Understands REST or HTTP by Argorak on Sunday February 26, 2012 @08:56AM (#3635616)
Isn't the whole point of REST/Hypermedia that the client holds the state instead of the server?