Comment 7 for bug 100620

The solution for: https://bugs.edge.launchpad.net/silva/+bug/100765
I'm thinking just setting up Silva Files and Images to be tied to a 'service_asset_cache_manager' would be mostly sufficient. Policies could be managed "per publication" by placing a new "service_asset_cache_managers" in that publication.

Or, this could be managed by metadata...a metadata list field with a TALES default that lists all cache managers available up the tree. The default selected would be the asset cache mgr.
Pro's:
i) can still set policies per container
ii) has fine-grained "per-asset" capabilities, given the policies are defined
Con's:
x) Whenever the metadata set is rendered this TALES will walk up the tree looking for cache managers
xx) This walkup includes Silva xml exports (what are the ramifications of this?), and Silva xml exports include public rendering of content.
I think this Con is true, but it would need to be verified.