On 10/11/06, craigdd <[EMAIL PROTECTED]> wrote:
I've read a couple times that with wicket 2.0 a feature has been added to allow developers to define if a Page is stateless or stateful. This feature is pretty nice and gets wicket a step closer to some of the features that JSF has and greately decreaes the size of the session in a large application.
the size of your application has no bearing on the size of the session. wicket-1.2 keeps an LRU cache of pages called a PageMap. wicket-2.0 only keeps a single page in session and dumps the rest to disk
With that said, has anyone gone a step further and though about have Page scoped somewhere between stateless and stateful? The basic concept would be the page is stateful as long as it is need and when not needed it is removed from the session.
what would be the usecase for a page like that? wicket keeps pages in session for backbutton support. I have really thought about how this would be implemented but maybe for
starters it is as simple as have a limit on the size of Pages in the session, when the limit has been retched then the oldest request Page is removed.
we already have a setting in 1.2 to limit how many pages are kept in session. and in 2.0 its not really necessary because only a single page is kept in session. -Igor
