Re: Making your webapp thread safe
but you only have a assignment in our session, and that assignment you do when somebody logs in the first time. After that it isn't used. So the only problem i can see is that maybe when you person logs in AND does already another request in another pagemap/browser tab then that tab will not see that it is logged in and also redirect once more. But what does that matter because if the second tab did came a little bit earlier any way then that would still happen. Its not that the session object will be in an inconsitent state at some point. johan On Jan 31, 2008 11:57 PM, Dan Kaplan [EMAIL PROTECTED] wrote: I've been told by many people that the Session object is not thread safe. If that's true, I don't think the example can be thread safe. RestartResponseException does not allow you to redirect to an external URL (that's what that method does). That's why I can't use it. -Original Message- From: Johan Compagner [mailto:[EMAIL PROTECTED] Sent: Thursday, January 31, 2008 12:18 PM To: users@wicket.apache.org Subject: Re: Making your webapp thread safe that looks fine i would throw a RestartResponseException in youre forcelogin method On Jan 31, 2008 8:48 PM, Dan Kaplan [EMAIL PROTECTED] wrote: Ok, I've asked this at least twice already but I'm still incredibly unsure of how to make my webapp thread safe. So this time I thought I'd take a different approach. I wrote on the wiki a short, unrelated example: http://cwiki.apache.org/confluence/display/WICKET/Facebook+Integration Is this example thread safe? If it isn't, please EDIT THE EXAMPLE TO MAKE IT SO. That way I can finally see a *complete* example of a thread safe webapp. Thanks a lot for any help ☺ Dan - 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]
Re: Making your webapp thread safe
that looks fine i would throw a RestartResponseException in youre forcelogin method On Jan 31, 2008 8:48 PM, Dan Kaplan [EMAIL PROTECTED] wrote: Ok, I've asked this at least twice already but I'm still incredibly unsure of how to make my webapp thread safe. So this time I thought I'd take a different approach. I wrote on the wiki a short, unrelated example: http://cwiki.apache.org/confluence/display/WICKET/Facebook+Integration Is this example thread safe? If it isn't, please EDIT THE EXAMPLE TO MAKE IT SO. That way I can finally see a *complete* example of a thread safe webapp. Thanks a lot for any help ☺ Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Making your webapp thread safe
I've been told by many people that the Session object is not thread safe. If that's true, I don't think the example can be thread safe. RestartResponseException does not allow you to redirect to an external URL (that's what that method does). That's why I can't use it. -Original Message- From: Johan Compagner [mailto:[EMAIL PROTECTED] Sent: Thursday, January 31, 2008 12:18 PM To: users@wicket.apache.org Subject: Re: Making your webapp thread safe that looks fine i would throw a RestartResponseException in youre forcelogin method On Jan 31, 2008 8:48 PM, Dan Kaplan [EMAIL PROTECTED] wrote: Ok, I've asked this at least twice already but I'm still incredibly unsure of how to make my webapp thread safe. So this time I thought I'd take a different approach. I wrote on the wiki a short, unrelated example: http://cwiki.apache.org/confluence/display/WICKET/Facebook+Integration Is this example thread safe? If it isn't, please EDIT THE EXAMPLE TO MAKE IT SO. That way I can finally see a *complete* example of a thread safe webapp. Thanks a lot for any help ☺ Dan - 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]
