Welcome to the hostile world of IE :-( It is particularly annoying when transferring a document (or other binary data) via https, where IE, 1) downloads the document, 2) clears (deletes) the cached (just transfered) document, and finally 3) launches the application that was supposed to display the now nonexistent document.
Alternately, you'll have occasions where IE will continue to maintain its cache even after you've cleared it, maintaining that you must not have been serious since you didn't restart the entire browser. For reference, development seems to go smoother when using other browser platforms (FF or Safari), simply due to the additional developer tools that are available (or included), and their not as quirky cache tendencies. -jason On Dec 15, 2008, at 2:24 PM, David Hoffer wrote: > > Jason, > > Sorry I'm not a web developer so I don't know the tricks yet. > > Regarding the cache, in my mind a good object API would provide a > boolean to enable/disable caching. But what is even worse is caching > that doesn't show any image. > > -Dave > > On Mon, Dec 15, 2008 at 2:16 PM, Jason Essington > <[email protected]> wrote: >> >> >> On Dec 15, 2008, at 12:22 PM, David Hoffer wrote: >> >>> >>> Oh, I see just a fake cache buster like ?<timestamp> does the trick. >> >> yes, that is what I was talking about ... >> >>> I wish GWT could have abstracted away this nonsense; >> >> well, if this sort of thing was included by default, then images >> could >> never be cached, reducing the efficiency of an application. >> >>> you would never have to add hacks like this with Java/Swing. >> >> Of course, java swing operates under a whole different set of rules >> and assumptions. >> GWT does help to make client side code a bit easier to develop, but >> it >> still ends up compiling down to javascript that ultimately is going >> to >> end up running in a browser ... some versions of which are decidedly >> hostile towards web developers. >> >> -jason >> >>> >>> >>> -Dave >>> >>> On Mon, Dec 15, 2008 at 10:23 AM, Jason Essington >>> <[email protected]> wrote: >>>> >>>> You could try attaching a cache-buster to the url ... append a >>>> timestamp or something to prevent the URL from being the same each >>>> time. >>>> >>>> -jason >>>> >>>> On Dec 15, 2008, at 10:15 AM, dhoffer wrote: >>>> >>>>> >>>>> My application makes extensive use of displaying dynamic images >>>>> via >>>>> the image#setUrl() method. >>>>> >>>>> The problem is that in hosted mode (Windows) if I try to display >>>>> an >>>>> image that HAS been previously displayed it will not load, instead >>>>> LoadListener#onError() is fired. However, If I manually clear the >>>>> cache of IE it will work again. >>>>> >>>>> It seems GWT thinks the image is in the cache but can't find it so >>>>> it >>>>> displays nothing instead of using the URL provided. Manually >>>>> clearing >>>>> the cache makes it clear to GWT that it should use the URL. >>>>> >>>>> How can I configure my app so that GWT will not try to cache >>>>> images >>>>> set via URL? >>>>> >>>>> Thanks, >>>>> -Dave >>>>>> >>>> >>>> >>>>> >>>> >>> >>>> >> >> >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
