On 11/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Martijn, > > isn`t this a problem of the framework itself? When I have page > constcted from serveral subcomponents then my JVM will run > out of memory after some user.
Well, every user (session) will use memory, correct. But only to a certain limit. Wicket 1.2 holds a couple of page/ versions in a session, and Wicket 2.0 by default only holds the current one. So the creation of a fresh instance (e.g. a bookmarkable page) will replace another one. Hence, how much memory you'll need is a simple function of the number of concurrent sessions times the size of your session and page(s) in it. 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&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
