The Installer 3.1 uses MD5 checksums on many of its downloads to verify their accuracy. The checksums for Google Closure Library, Adobe AIR SDK and playerglobal.swc change every once in a while and that breaks installs until we find out, download the file, compute the new checksum and update the sdk-installer-config-4.0.xml file on the web-site.
Is there a way we can automate that? The Adobe AIR SDK is over 200MB (times 2 platforms) so it would be a lot of bandwidth to keep downloading it. Is it possible to implement quicker check the way browsers verify what is in their caches? Thoughts? -Alex
