The user would have to reset their clock and make the request at the
EXACT SAME MILLISECOND in time. It's nigh impossible. It will never
ever ever EVER happen. You're good to go.
var d:Date = new Date();
var noCache:String = String(d.getTime());
var xmlPath:String =
Bellerive [mailto:[EMAIL PROTECTED]
Sent: 03 March 2007 03:54
To: flashcoders@chattyfig.figleaf.com
Subject: [Flashcoders] Cache Killer... is it bulletproof ???
I've read that appending a random query string ( example :
new Date.getTime() ) to the URL of assets (images, sounds,
XML files
Actually using a random string is not a good idea because there is a
chance, however small, that it will fail. Using new Date().getTime(),
as the OP mentioned (and erroneously called random), will work every
time (unless, of course, the user resets their clock during the
session--and even then
I've read that appending a random query string ( example : new Date.getTime() )
to the URL of assets (images, sounds, XML files, etc.) loaded at runtime in the
Flash Player ensures that these assets are always loaded from the server
instead of being loaded from the cache.
I've tested this on
Is this method bulletproof (it works in all browsers on all operating systems)?
Is this something that you would really rely on for big projects?
Has anyone ever used this method and had big problems with it or even minor
glitches?
It is bulletproof. There's no reason why it shouldn't work.
Hi David !
Yes this mostly seems to work quite well. The thing is to make sure that
all assets are called using this random string-- that none sneaks
through unintentionally
Kind regards
Prema
David Bellerive wrote:
I've read that appending a random query string ( example : new
6 matches
Mail list logo
