What I want to avoid is a (web) session full of pages (components). For example, suppose someone who navigates through several pages. Each page is then stored in his/her session. We, then, end up with an overloaded session that is cleared only when timeout or logout.
Suppose also an employee who trying to "edit" several items at once. To do this, this employee opens a browser tab per item. If this task spans more than one request i.e. different screens, I think we highly need a conversation... Once a conversation is finished, the components AND the models (IModel) living in this conversation would be cleared. Thanks -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-workspace-tp3451294p3451589.html Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
