I've worked on a couple applications in the past were they have decided not to use the HTTP Session and instead create their own structure, basically a session type of object gets stored in the database per request. Although I don't really love this direction but I have seen some benefits. My question regarding to Wicket is has anyone done something similar while using Wicket? How easy / feasible would it be to have the Wicket session backed by an applications own structure? -- View this message in context: http://www.nabble.com/Wicket-Session-backed-by-something-other-than-HTTP-Session-tp14741289p14741289.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]
