Influencing Browser Caching with Sencha Cmd for an ExtJS 4 App
Is it possible with Sencha Cmd to add a parameter to a script src property to encourage browsers to dump their cached version of the file?
Right now Sencha Cmd turns this:
<!-- <x-compile> -->
<!-- <x-bootstrap> -->
<!-- </x-bootstrap> -->
<!-- </x-compile> -->
We're running into a minor but annoying problem. Browsers are caching the all-classes.js file and when we push changes (which we do quite frequently, every other day or so) not all users get them until some time later.
Is it possible to use Sencha Cmd to instead generate something like this:
Where version is just some random number or timestamp that is added so that each time you run Sencha Cmd browsers will see the new parameter and replace their cached versions?
P.S. My backup plan is to just do this myself using SED or equivalent as part of our deploy process, but figured I wouldn't re-invent the wheel if Cmd could already do it for me. Looked in the docs, didn't see anything about this.
+1 for the feature request of making cache busting a part of Sencha CMD
Good question and clear answers by the way... thnx!