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.
Looking for confirmation I found this statement in [HTML5 Audio - The State of Play](http://html5doctor.com/html5-audio-the-state-of-play/):
>Until fairly recently, the load method was required in order to tell the browser about a change in the media source and to get it to update appropriately. Now, **media.load() causes the element to reset and to start selecting and loading a new media resource from scratch.**

So I agree that this is probably unnecessary. Are you asking *me* to remark it out or delete it?