>>What if you don't care if its cached, or would actually like it to be cached?
If you refer to my post, I suggested an option to not cache, so would
be cached if not specified, as it should be.
Trust me (or trust google), headers won't always work even if you got
ie7 to behave. The url trick is
Big problem on Opera too.
Don't bother with headers, they don't work and are more difficult.
You MUST add a variable to the url: + new Date().getTime();
Easy enough to add to your calls, but I'm surprised it's still not in
the ajax function as an option because a common problem. Earlier
threads
>All I'm saying is that jQuery supports an
> ifModified option for Ajax requests and that I'm not sure if that option
> still works as expected with an automatic time stamp added to each request.
I see. I would assume not bc a different url.
Btw, I wouldn't want an automatic stamp added either.
There are problems with IE and headers on GETs, Klaus. The timestamp
is flawless and easy. See here for example: http://www.enja.org/david/?p=25
Can anyone suggest good code to wrap jquery in to wall it off from
older browsers altogether? I'd prefer some object detection but
obviously createElement isn't going to cut it finely enough. I'm not
up on what the latest browsers have that IE5.5/OP8 and others don't
have.
As I wrote on another t
> I think it's not that easy.
I believe it is. Used it for years. Other APIs do it too, I recall.
> *shrug* Easy enough to add. Stick an extra key/value into your params.
of course, just found it strange it wasn't an option because a common
problem and solution going back years.
> Right, which is why I test on all the browsers in the projects specs.
> Thankfully most of our projects are IE >
Thanks to all. That cleared up some stuff.
By overhead I meant processing time and memory usage.
I hadn't seen the timeout call the error handler and thought it just
canceled the call after looking at the code. Thanks!
An option to add a timestamp to NOT cache ajax GETs is what I meant.
It woul
>>IE completely refuses to load the page at all,
instead alerting me about something like "can't display this page", so
quite impossible to debug.
This sounds like the weird bug in IE when you modify the dom before
the page is ready. Something on msn developer about this.
I've rewritten my site scripts with jquery and eliminated a bulky menu
script, 2 different image viewers, ajax/rpc script I did years ago,
and a bunch of other bits, now all packed down into about 26kb total
including jquery and with more functionality :-)
Some random newbie questions you hopeful
10 matches
Mail list logo
