Would it be possible to generate resource paths with a version string
in them so that browsers will cache resources, but request new ones
when a version has been bumped?

e.g.

http://example.com/resources/org.apache.wicket/wicket-1.4.1/wicket-ajax.js
http://example.com/resources/nl.topicus.project/project-2.0-12341/project.js

Used this way we can let those resources never expire, taking only a
hit for the first time the resources are requested.

Perhaps 
http://example.com/resources/org.apache.wicket.wicket-ajax.js?version=1.4.1
works also, but something tells me browsers might not cache this.

Martijn

Reply via email to