|
|
|
[
Permlink
| « Hide
]
Raoul Zon - [14/Jun/06 05:02 PM ]
Has anyone have chance to look at this issue, or has it been downgraded on priority?
Our focus is on bug fixing the current release and on releasing the version 3.0.
I was about to post the same ticket when I saw this post.
It's not a big deal to me if the jsp/runtime application is provided to tune these settings, but what we really need is the ability to dynamically change the values. In line with what I believe the original poster had in mind, this would entail nothing more than providing getters/settings for the servlet filter parameters. This would also allow inversion of control containers to set the values dynamically. I'll gladly submit such a patch if the OSCache developers are focusing on 3.0 instead for now. Danny, of course you can provide a patch based on the current revision of the CacheFitler: http://svn.opensymphony.com/svn/oscache/trunk/src/java/com/opensymphony/oscache/web/filter/CacheFilter.java
Do you want to set all upcoming CacheFilter configuration parameter?
time scope cron fragment nocache lastModified max-age expires ICacheKeyProvider ICacheGroupsProvider EntryRefreshPolicy oscache-properties-file Yes, basically, anything that could safely be modified once OSCache is running would be a tremendous asset. For example, any of the time-specific options should be tune-able via some sort of GUI, like: lastModified, max-age, expires, etc. I could see how changing the KeyProvider could be a problem once the cache has been populated, but for the most part, it seems like many of these could safely be modifiable while OSCache is running.
getter/setter for 'oscache-properties-file' is still open.
TO DO: Document spring integration. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||