Re: Twisted and reverse proxies

On Wednesday 31 March 2010, I wrote:

> An alternative would be to compute a hash of the static content and use
> that hash the URL. That way you would not need an application restart
> when static content changes.

I just realized that this would make it very difficult to have one static 
resource (style sheet) refer to another static resource (image). Unless you 
would rewrite the referring resource, but then it's not really static 
anymore.

The approach with an ID generated at startup does not have this problem, 
since the ID can be put in the URL as a path element and all references 
between static resources can be done as relative URLs.

Bye,
		Maarten