Food for thought around the AppCache feature which can be similarly affected i think.
---------- Forwarded message ---------- From: emu <emu.hu...@gmail.com> Date: Sun, Sep 20, 2009 at 8:31 AM Subject: [gears-users] Version in manifest is not enough To: Gears Users <gears-us...@googlegroups.com> Some times the response of the web server be changed by some proxy servers or even the ISPs(some times they try to add some ads or filter something), and google gears will cache the changed content an will not check before the manifest file change again, and some times the manifest files change before the files they list changed because of the CDN problem. When these happends, wrong captured files becomes a disaster. It's very hard to findout what happends to the clients' browser. If gears has a second-check option, like this: { "url": "abc.html", "md5": "92d9b0186331ec3e" } it'll be very very helpful.