Express migration + website caching

I am recommending this code be merged with the main branch immediately. We have discussed it a lot on the dev group. I just tested a javascript alert in client.js, which was immediately displayed on the first reload (reload button only, no shift required). I also changed the text and the change was again displayed on the first reload.

This tells me the new caching mechanism is recognizing when the files have changed. I believe this proves our code changes will be recognized immediately.
Removed.


On July 1, 2014 at 12:54:16 PM, Ben West (notifications@github.com) wrote:

In static/js/client.js:

>   
>      $('#testAlarms').click(function(event) {
> +        d3.select('.audio.alarms audio').each(function (data, i) {
> +          var audio = this;
> +          audio.load();
If you wouldn't mind deleting it, I can send you patch if you want. I'm pretty happy with this, it's soft caching which does not prevent updates. While more caching could be done, I think simply removing all the `load`s alone will accomplish quite a bit. Having added the soft caching like we have will also continue to help. This particular caching should not require any cache busting (except to fix the overly aggressive cache now) once everyone is using this, we can iterate on smarter or stronger or softer caching. If Adrien agrees, let's roll with this soon.
…
—
Reply to this email directly or view it on GitHub.