Don Box: GET is one of the most optimized pieces of distributed systems plumbing in the world. It’s an absolute/objective slam dunk. No arguing/evangelism needed IMO. GET is the classic “the first bag is free” kind of feature a platform builder dreams about.
The optimizations that GET provide are cheap, but not free. I continue to use my elevator pitch frequently.
I’m guilty of spreading this “REST/GET == cacheability” story, without providing the bad news that you need to work for it. ETags, Last-Modified, Expires, etc. No cacheability without it. The server needs to do a little work to make this happen. And your data might be implicated.
I’ve collected lots of somewhat REST-connected posts in the last two weeks, but somehow can’t seem to find the time to comment … so here’s a quick linkdump: Verbs and Interaction patterns, Benjamin Carlyle, including some interesting thoughts on a gateway approach between WS-* and REST Mark Nottingham on REST issues, real and imagined — good points, especially regarding URI......
[more]
I’m guilty of spreading this “REST/GET == cacheability” story, without providing the bad news that you need to work for it. ETags, Last-Modified, Expires, etc....