Comment on When REST isn't Good EnoughparentComments−Domenic_S13yI cringe a little bit whenever someone tries to present caching as simple or straightforward.−drivebyacct213yI 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.−jebblue13yThe 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−Ramone13yGET 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...−drivebyacct213yI meant the HTTP spec which is where GETs specified.
Comments
I cringe a little bit whenever someone tries to present caching as simple or straightforward.
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.
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
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...
I meant the HTTP spec which is where GETs specified.