News for hackers. Stuff that matters.
Re:When REST isn't Good Enough by Domenic_S on Tuesday November 20, 2012 @02:33PM (#4810831)
I cringe a little bit whenever someone tries to present caching as simple or straightforward.
Re:When REST isn't Good Enough by drivebyacct2 on Tuesday November 20, 2012 @02:44PM (#4810907)
I don't see that anywhere in the post. All I saw was "GET"s shouldn't modify state and should be cacheable. That seems perfectly in line with the spec.
Re:When REST isn't Good Enough by jebblue on Tuesday November 20, 2012 @05:19PM (#4811662)
The only problem I have with your comment is that REST is not specified, it's a style:

http://en.wikipedia.org/wiki/Representational_state_transfer

Re:When REST isn't Good Enough by Ramone on Tuesday November 20, 2012 @07:01PM (#4812026)
GET being cacheable/idempotent is part of the HTTP spec, and has nothing to do with REST: http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13...
Re:When REST isn't Good Enough by drivebyacct2 on Tuesday November 20, 2012 @06:14PM (#4811898)
I meant the HTTP spec which is where GETs specified.