On 5/17/06, Bruno Borges <[EMAIL PROTECTED]> wrote:
Will Wicket take care of cleaning up the HttpSession sometimes in a while?
I mean, we create lots of components, for lots of pages the User is
accessing. How Wicket know which objects must be removed and with which
frequency it will do that?
Yep. By default we use HttpSession as a session storage, and
HttpSession objects will automatically be cleaned up by the session.
If you use an alternative store (ISessionStore), you'll be notified
when the session invalidated.
How this mechanism works? I'm worry about large projects.
It's actually something that is very good for projects, as - if you
play by the rules of Wicket - there won't be a need for much ad-hoc
session usage which you typically see at projects that don't do state
handling. Topicus profiled some of their applications a few months
ago, and found out the apps that were build with maverick (model 2
framework) actually ended up with a lot more memory usage because of
that. So while one of the 'prices' you have to pay for using wicket is
that you'll always use session memory, one of the things you get for
it is that the ammount of consumption is much easier to control and
predict/ profile.
I'd say look at how ISessionStore works, and get back on the list for
remaining questions.
Eelco
---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
