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 =
Also check out my blog entry on the subject -
http://blog.neo-archaic.net/2006/08/02/nocache-for-javascript-and-flash.htm
The Flash IDE doesn't like the cache-busters so you need to test
System.capabilities.playerType before appending the query.
Karina
-Original Message-
From: David
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
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
5 matches
Mail list logo
