Hi guys, I'm developing a portal/forum application for my dissertation and wanted to display a panel with all currently active users. Now I found an old thread (Wicket 2.0) where Eelco posted an example SessionStore implementation to solve this specific problem, but that raised some questions.
1. Should I subclass HttpSessionStore or SecondLevelCacheSS? What is the back-button problem with HttpSessionStore? Is there another way to solve this? 2. Eelco's implementation seems to be memory only, why would I want that? What are the advantages/drawbacks? Should I implement a custom database specific session store? 3. Not that I'm hitting a million users any time soon, but what would be the best approach in terms of clustering, just out of interest? Thanks in advance Marco -- View this message in context: http://www.nabble.com/Tracking-logged-in-users---SessionStore-questions-tp19273568p19273568.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
