Okay, that makes sense. Thanks a lot!
On Sun, Aug 24, 2008 at 3:00 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > yes. Explicitly binding won't have an adverse effect if that is your > intention. Delayed (http) session creation is done to prevent an easy > DoS vector (though if your application at some point does create a > session, someone will find out and there you are...), and improve > scalability—having no session means not having to distribute that data > across the cluster. > > Martijn > > On Sun, Aug 24, 2008 at 11:14 PM, nate roe <[EMAIL PROTECTED]> wrote: >> The use of Session.bind() has resolved my problem. >> >> If I have a bookmarkable login page, then, I suppose I should bind the >> session before storing the user's data to the session? >> >> On Sat, Aug 23, 2008 at 9:15 PM, brian.diekelman <[EMAIL PROTECTED]> wrote: >>> >>> It depends on the situation and your logging setup. Do this to verify: >>> >>> - First put a logging statement in WebApplication.newSession(), not >>> MySession.get() >>> >>> - Open a new browser window and go to your 'verify' bookmarkable page. You >>> should see a new session created on each refresh >>> >>> - Now put 'getSession().bind()' somewhere in your page constructor. >>> >>> - Cycle/redeploy the app and go to the 'verify' bookmarkable page. You >>> should only see one session created, and it should reuse that session on >>> each refresh. >>> >>> >>> If any of the above didn't happen as described, that's what I would call >>> unexpected behavior. Otherwise, what was the expected vs actual behavior? >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Session-creation-tp19123581p19127645.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] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
