yes, using stateless pages when it's possible will definitely reduce
your session size. Wicket offers a stateless version for those
components which by default have a stateful nature, like forms and
links. As general rule you can implement a stateless page when the page
doesn't need to keep its internal state between two consecutive
requests. For more information on stateless pages see live examples at
http://www.wicket-library.com/wicket-examples/stateless/
Hi,
I need some suggestions. In my wicket application (in development phase), I
have used normal forms and links. While going through the concept of
stateless pages and forms, I am confused about converting the forms and
components to stateless. Will it really minimize session usage in the
system. I need to minimize it as i wont be having much server space
initially.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Need-suggestion-on-minimizing-session-usage-in-wicket-web-application-tp4650956.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
