i really wish sometimes that wicket were my job... there's so much stuff like this to explain and/or dig into and/or implement... and i just can't make the time most days!
Kamil Rembalski wrote:
Hi,
I remember that some time ago there was a discusion on caching the images for roundCornerPanel. the images should be generated only once per page. Did you think about introducing something like component scope? I think that this would solve the issue to some extend and would be a generally nice feature. Apart from components stored in session, there could be page-scope components (created once per page class) and application components, created once for the whole application. This could improve the memory efficiency (do not create an instance of component for each user if can use the same component). It could also improve performance of applications written in wicket - while writing my sample application I have noticed that about 60% of components display the same data for all users and could therefore be stored sowhere in the 'application scope'. What do you think about this? I am completely not sure if it is a good Idea, and it's pretty high-level...
regards, Kamil
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
