addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1light-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

sthlm.js Message Board › Follow up: jQuery AJAX cache issues

Follow up: jQuery AJAX cache issues

A former member
Post #: 4
1. Links to articles on the same topic - so I'm not completely alone in this field:
- http://www.sitecrafti...­
- http://www.electricto...­

2. Even Paul Irish seems to have been working on something more or less identical it seems, but extending jQuery:

I'm not trying to rest my case, rather would be happy if someone could state I'm 100% wrong, e.g. "browsers is actually reading the specs". :)
Andreas W.
user 11790179
Stockholm, SE
Post #: 1
Okay the browser is dumb.

Then force it to reload by changing the url, ex add a ?_dc=
But then the server will think it's a new request. So you have to fix so server controls request to local cache and if same return type 304, if modified send new data (might be possible to do with VCL in Varnish).

This probably only works if you use a cache manager on the client, like the one you made with localStorage/sessionStorage. Just so you control when a request is made to the server.
A former member
Post #: 5
The point was not really "cache is not invalidating", the point is "sometimes it's cached, sometimes it's not". Invalidating can be done as you propose - in fact I already use that technique for iframe-hacks, but not the other way around in a reliable way naturally. That's why I'm handling it with client-side caching using localstorage, and as a bonus I don't have to make the connection in the first place in say 5-20 min depending on "server health": scalability + reliability (in a annoying way).
Powered by mvnForum

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy