GWT's perfect caching is pretty similar to this - Use the MD5 of the file contents as the filename, and send out 'cache forever' headers with the file. Thus,

GWT's perfect caching is pretty similar to this - Use the MD5 of the file contents as the filename, and send out 'cache forever' headers with the file. Thus, if the file hasn't changed, the browser doesn't even need to make a HTTP request/wait for a 304 response. The MD5 filenames are stored in a 'never cache' bootstrap. http://code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#perfect_caching http://code.google.com/webtoolkit/doc/latest/DevGuideCompili... I'm surprised i don't see this type of thing more often in other libraries.