change JS/CSS file fingerprinting, so it's impossible to accidentally forget to use versioning

[GoogleCodeExporter]

the current JS/CSS file versioning scheme uses an urlparam (&zx=),
which is vulnerable to developers accidentally forgetting to use it,
either when referring to an existing file, or when adding a new file.

the strawman proposal is to:
 - register /v to a handler which requires /v/{some string}/path/to/file
   and responds with the contents of /path/to/file
 - deregister static file paths to /css and /js, so we don't
   accidentally refer to them in new HTML.

given the code freeze, I'm tagging this for right after the initial release.

Original issue reported on code.google.com by adam.sah on 17 May 2009 at 12:18

[GoogleCodeExporter]

Original comment by adam.sah on 20 May 2009 at 5:14

• Added labels: ConsumerUI

[GoogleCodeExporter]

Original comment by adam.sah on 5 Jun 2009 at 2:45

• Added labels: Milestone-Release1.5

[GoogleCodeExporter]

another reason to do this is site speed:
http://code.google.com/speed/page-speed/docs/caching.html#LeverageProxyCaching

Original comment by adam.sah on 6 Jun 2009 at 4:20

• Added labels: Latency

[GoogleCodeExporter]

fixed in r722.

Original comment by adam.sah on 8 Jun 2009 at 12:24

• Changed state: Fixed