You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Dominik Drzewiecki (Updated) (JIRA)" <ji...@apache.org> on 2011/11/12 10:08:51 UTC
[jira] [Updated] (WICKET-4221) Provide IResourceVersion
implementation that does caching but provides means of updating cached
entries.
[ https://issues.apache.org/jira/browse/WICKET-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominik Drzewiecki updated WICKET-4221:
---------------------------------------
Attachment: UpdateableCachingResourceVersion.patch
It is largely based on CachingResourceVersion and uses synchronized LinkedHashMap as an underlying cache storage which may impose some scalability issues.
> Provide IResourceVersion implementation that does caching but provides means of updating cached entries.
> --------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4221
> URL: https://issues.apache.org/jira/browse/WICKET-4221
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.5.3
> Reporter: Dominik Drzewiecki
> Priority: Minor
> Attachments: UpdateableCachingResourceVersion.patch
>
>
> Now, you either have the entries cached for the application lifetime or you need to recalculate the version on each resurce link generation. Both implementations have their drawbacks. I hereby propose an implementation of IResourceVersion - UpdateableCachingResourceVersion - that may be initialized with the rule specifying how often/when the call should be redelegated to underlying provider and thus update cached entry.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira