Which raises an interesting question about using Atom and RSS and indeed HTTP, because while you can indeed set a cache request (or no-cache request) on the document there is nothing to stop the other end making an arbitary decision. Now this certainly makes Google quicker to respond to subsequent requests, but it doesn't make the information more reliable. Now clearly the folks at Google have made a smart trade off between performance and information latency. But by making that trade off its made my service less responsive.
What a cracking example of the problems of the networked world... easier my arse.
Technorati Tags: Google,