We have sites that are heavily using external javascript files. And when new features are implemented that also means we have to edit these files. Some browsers, I'm looking at you Chrome, does some heavy caching and are reluctant to reload these files unless forced to.

This is no issue for us developers, we know how to do this, and know when to do it because we did the change and know it's required.
But the general visitor does not know. They will risk getting an confusing error, or no reaction at all, because their browser is using an outdated javascript file.

Now, that browsers cache reused resources is not a bad thing. Only if the resource is outdated.
What would be the best approach to have browser understand when to reload shared stuff and when to use the cache? Without ever having us to force a reload.

HDB
Jolle

#############################################################

Attend the Lasso Developer Conference 2013!
Sept 12-14, 2013 in Niagara Falls, Canada
http://www.lassosoft.com/LDC-niagara-falls-2013

#############################################################
This message is sent to you because you are subscribed to
the mailing list Lasso
Lasso@lists.lassosoft.com
To unsubscribe, E-mail to: <Lasso-unsubscribe@lists.lassosoft.com>
Send administrative queries to <Lasso-request@lists.lassosoft.com>