Hi,
As part of the fix for bug #1260087 I've added this new mechanism for
controling the lifecycle of resources:
Resource.setIdleTimeout(Duration value)
DynamicImageResource.setCacheTimeout(Duration value)
When a resource is hit, the idle timer is reset and we begin counting
again. When a DynamicImageResource cache timeout occurs, its cache is
flushed -- the next time it is hit it will have to re-render the image.
When a Resource idle timeout occurs, it is removed as a shared resource
-- the next time it is hit it will result in a HTTP 404. When users hit
the page containing the images they are repopulated it they were removed.
I set my cache timeout to 5 minutes and resource idle timeout to 30
minutes. Application-scoped resources default to a timeout of zero and
so they are not affected by this.
This results in huge memory savings and improved performance in
applications which are very resource-intensive like
http://www.desktopbeautifier.com/
I hope you guys like this new design. Let me know what you think.
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
