On 20.09.2010 02:37, Aryeh Gregor wrote:
... Sure it would. You can currently only save an HTTP request if a future Expires header (or equivalent) can be sent. A lot of the time, the resource might change at any moment, so you can't send such a header. The client has to check every time, and get a 204, even if the resource changes very rarely. If you could indicate in the HTML source that you know the resource hasn't changed, you could save a lot of round-trips on a page that links to many resources.
> ...
Resources that should be cached (stylesheets, images) but change at unexpected times are indeed a problem.
A well understood approach is to push some kind of version indicator into the URI (such as query parameter).
Best regards, Julian
