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
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
Thanks Jason, I could try this as a test. However I have several
'default' images these dynamic images revert to if not set and it
would be a huge hack/pain to have to create duplicates of these with
random/unique names. Is there not a way to just turn caching off?
-Dave
On Mon, Dec 15, 2008
Jason,
I guess it would also be okay if caching was on AND that caching
worked. The problem is that caching is on and does not work.
-Dave
On Mon, Dec 15, 2008 at 10:32 AM, David Hoffer dhoff...@gmail.com wrote:
Thanks Jason, I could try this as a test. However I have several
'default'
Oh, I see just a fake cache buster like ?timestamp does the trick.
I wish GWT could have abstracted away this nonsense; you would never
have to add hacks like this with Java/Swing.
-Dave
On Mon, Dec 15, 2008 at 10:23 AM, Jason Essington
jason.essing...@gmail.com wrote:
You could try
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
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
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
