"Mart" <[EMAIL PROTECTED]> writes:
Everything is fine and jolly in Firefox, Opera, etc, but not in IE. As
many of you probably already know IE has a habbit of caching pages and
async JS requests to server. (And no, at least at the moment, I have
nothing against caching the results.) So, why isn't that code working
and what has it to do with caching?
Are you adding something to change the URL on each and every request?
How have others dealed with such situation? Is there any trick to
getting the callbacks attached before the async request is made? If
there isn't, then why?
There are. Some of them mentioned on this mailing list recently. You should
attach a throw away parameter on your URL to foul IE... The recommended
approach is using the current timestamp:
================================================================================
// Avoid caching on IE...
function timestamp() {
return new Date().getTime();
}
================================================================================
Then, on your URL:
URL = URL + '&throw_away=timestamp()';
;-)
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~----------~----~----~----~------~----~------~--~---
