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.
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. 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. Just a thought, it might be a winning featuer that JSF doesn't have. -- View this message in context: http://www.nabble.com/View-Scoped-Pages-tf2425546.html#a6763108 Sent from the Wicket - Dev mailing list archive at Nabble.com.
