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