do you have a benchmark that shows that pooling is indeed faster? servlets are pooled because they may require heavy initialization. wicket pages are much more lightweight in comparison.
-igor On Sun, May 18, 2008 at 4:36 AM, Joel Halbert <[EMAIL PROTECTED]> wrote: > Johan, > > Although the pages are stateless, they can still be pooled, and > "re-initialised" (their state cleared out) between requests. > This is indeed what many java servlet containers do with stateless Servlets. > It is also the a technique used by Tapestry 5 to achieve greater > scalability. > > Rgs, > Joel > > -------------------------------------------------- > From: "Johan Compagner" <[EMAIL PROTECTED]> > Sent: Sunday, May 18, 2008 12:27 PM > To: <users@wicket.apache.org> > Subject: Re: Page pooling (for stateless pages) > >> For stateless pages?? >> The whole point of stateless is that they arent kept in the >> session/memory. >> >> And pooling pages is not really what you want any way, you can only >> pool then for a single user/sessiion so you would have a pool for >> every session. >> >> And when do you decide to return a pooled page? >> >> On 5/18/08, Joel Halbert <[EMAIL PROTECTED]> wrote: >>> >>> Hi, >>> >>> I was wondering whether it was possible to implement "pooling" of >>> stateless >>> pages? Possibly using a custom PageMap implementation? >>> >>> Although newer JVM's are good at performing GC, pooling is a reasonable >>> additional technique to use for achieving that extra bit of scalability. >>> >>> If anyone has tried to do this, or has any suggestions on the best way >>> forward I'd be really interested to know. >>> >>> Many Thanks, >>> >>> Joel >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
