Comment 7 for bug 100765

It is possible to automatically configure FSObjects to use a predefined cache manager.

I created an accelerated http cache manager, service_static_cache_manager. (also caching non-anonymous requests) I took an image in globals, 'ranking.gif', and added a metadata file 'ranking.gif.metadata'. In this file, I placed the following:
[default]
_Cacheable__enabled=1
_Cacheable__manager_id=service_static_cache_manager

I restarted zope, shift+refreshed the image in Firefox with livehttpheaders active. The accelerator was called when the object was rendered, so this procedure will work.

The only slight-negative is that all files will need a .metadata file associated with them, which contains the content from above. So, think hard now about what you want this http accelerator to be called!

This approach could also be taken for various SilvaViews filesystem assets.

There's no documentation anywhere about these .metadata files, so wrote one up, here:
http://altepeter.net/tech/articles/fssite_metadata

Please advise on how you'd like to proceed here. I'll be happy to add .metadata files for these, and look into adding for static css, js, and image assets in the views as well.

This should greatly improve cacheability...for now (at Bethel), since we run Silva behind Apache, I've been using Apache to set the cache headers.