Percolating REST
Larry O'Brien: This article and this one (both by Paul Prescod) and this one by Sam Ruby I think are finally getting through my thick skull why "REST" is being used as a proxy statement for "the challenges that many Web Service developers will face." They're much better reading than the REST Wiki. Cool. By the way, I believe it was me that "cheekily" said that one needed to "get prepared for the object reference to move outside of the parenthesis".
I also agree with your "on the other hand" comment. It gets worse, however. If I have a reference to a.b.c, and then I do a PUT to a, it is not always clear what the caching implications to a.b.c are. This is a subtle point that often gets glossed over.
It's even worse than that.
Say that a just returns a list of subobjects (b) with their subobject (c) counts.
In that case, a's cache could be invalidated by a put to a.b which creates c.
Posted by Michael Bernstein at