Tweaked a bit and committed, thanks.

Yea, just me being overly cautious again :)



Convinced...

Is the administrator task to wonder about cache. No other modules 
wonder about it, I don't see a reason why doing it here.





If you need an periodical clean up for your file based cache you can 
add a cron job like this



for s in $( find  cachedir -mtime -1 ); do

     rm s

done



This will delete all files older then one day.

Why? If there are concerns about the amount of data in a cache on a 
backend that doesn't already limit it (like memcache), users can run 
pruning scripts (or we can add limits if really necessary).
I just don't see this as a concern. If we end up spending a lot of 
time caching data that's never used in the cache, that's one thing, 
but shares are pretty static and accessed often.

I like the idea in general, but I'm hesitant to allow the storage of a 
potentially large number of shares in the global cache.  I know you 
have a fairly large userbase, any ideas on memory/disk/whatever 
consumption?



Plus, this should probably be a seperate config in addition to the 
general cache config since it potentially stores large number of shares.



Any one else with thoughts?

We can control where a share changes, and they not change often. So 
cache them if "usecache" configuration option is enabled.