If you were to add in pooling, you'd have to either provide a new hook (new lifecycle method) or a warning to the user (as you mentioned) that they have to rollback the state themselves after rendering using onAfterRender() or something.
On Sun, May 18, 2008 at 8:23 AM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > I agree with Johan. Stateless in Wicket sense means that we don't keep > the page in memory but recreate it from scratch. This means that we > don't roll back state. Pooling requires us (the framework or the > users) to rollback any state that was accumulated during rendering. > This is really not an avenue I want to pursue. > > Martijn > > On 5/18/08, 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] >> >> > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.3 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 > > --------------------------------------------------------------------- > 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]
