On Dec 11, 7:49 pm, Mike Williams <[email protected]> wrote: > The tileoverlay .refresh() call simply tells the API to re-execute all > the .getTileUrl() calls. The API doesn't force the browser to flush its > cache, so if the URL generated by .getTileUrl() is the same, the browser > may try to use the data in its cache. > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team
Is there actually any "legal" way to make a browser flush its cache through js? All I've seen in my (admittedly brief) googling is stuff about doing an unload/reload and that it works, sometimes. Although, for anyone following the thread, I think I've come up with the not-quite-magic-bullet. IE's behavior is _better_ with the cache- control headers AND url rewriting. With just cache-control, it reloads from cache if the same tile is requested. With just url rewriting, it leaks like a manic. With the two together, it still leaks, but it's a lot less than it was. I presume that it's realizing that after a little while, there's no reason to be caching something the server told it NOT to cache and that has never been re-requested. (I'm also put in a dump/recreation of the overlay after 10 refresh recalls but my testing hasn't gotten to the point where it was going to be activated yet. Too much other stuff I'm still tracking down.) Deirdre --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
