[Zope3-Users] best practice for serving static content by front-end webserver?

[Sascha Ottolski]

Am Sonntag, 14. Januar 2007 09:49 schrieb Lennart Regebro:
> On 1/13/07, Sascha Ottolski <sascha.ottolski at lalisio.com> wrote:
> > Now, when grepping the zope sources, and third party packages, the
> > included files are spread around. that seems to make it impossible to
> > write proper rewrite rules. if a request wants
> >
> >         /++resource++/image.gif
> >
> > the webserver couldn't possibly know if image.gif is found in
> >
> >         app/Zope-3.3.0/lib/python/zope/app/i18n/browser/
> >
> > or in
> >
> >         app/Zope-3.3.0/lib/python/zope/app/rotterdam/
> >
> > or in various other directories that carry images.
>
> It seems that your objective is to not have Zope serve images. 

correct, I would like to delegate this to the front-end webserver.


> I think the easiest way to do that is to use a cache that has a very long
> cache-timeout for images. I've found "Varnish" to be very flexible and
> useable.

thanks for the pointer, looks promising.


> The way to figure out where an image is located and then returning it
> is called "traversal" and Zope already does that, and you are unlikely
> to actually be able to make it signficantly faster that Zope already
> does. ;)

fair enough :-) anyway, I still would argument that it is suboptimal to 
generate different URLs for the same static object as in

<img tal:attributes="src context/++resource++zope3logo.gif" />

both for the the proxy, and the caching the browser handles itself. or am I 
missing something here?


Cheers,

Sascha

-- 
Lalisio GmbH                                www.lalisio.com

Puschkinstraße 1                   fon +49-(0)361/541 43 80
99084 Erfurt                       fax +49-(0)361/541 43 79
                                        kontakt at lalisio.com