there is an elegant solution to your problem which has nothing to do with browser refreshes. take a look at the images example.
ImagesApplication.getCancelButtonImageResource() holds an image resource that can be shared and utilized throughout an application (since resource images in wicket have a stable url) without ever regenerating it (unless you want to).
Gili wrote:
I noticed that when I hit REFRESH in the browser over and over again these resources keep on getting regenerated. This is caused by the fact that every time the user refreshes the browser, a new Page is generated and a new set of RenderedDynamicImageResource objects get generated.
My question is: isn't there a way to tell Wicket to not generate a new Page object every time the browser refreshes? Or at least, if it must do that, make it smart enough to not regenerate all these resources?
Gili
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
