On Mon, May 5, 2008 at 10:37 AM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > isnt this also a regular limitation of clustering? if you have a > complex object in httpsession and change one of its properties it wont > necessarily get replicated unless you set the actual httpsession > attribute again. some clustering libs only replicate dirty properties, > not entire sessions. so i dont necessarily think calling dirty() once > an attr changes is that big a deal, especially given you will not have > that many of those, with wicket there isnt much reason to keep things > in session yourself. >
I don't keep things in the session myself. I have a web of session data. Each of my submodules adds a property to the root session object. So, in my session class I have getModule1Data() and getModule2Data().
