The answer in both cases is: nothing. The session and its scoped variables are unaffected.
Of course, in the second case, the session (and its variables) are not accessible by the second web app and will eventually time out. [ May 22, 2008: Message edited by: Bear Bibeault ]
Thanks for answering. In the case (2), say in my first application I created a session and then redirected the request to different application. So you mean to say that I cannot access the session attributes here? Please explain. But within a timeout period if I redirect my request from this application to the one where I created a session what happens in that case, will I be able to access the session and session attributes back again?
Sounds like something that's simple enough to test with a few simple classes. What happens when you try it?
nandkishor rao
Ranch Hand
Joined: May 24, 2006
Posts: 53
posted
0
I know that simple enough to test but my problem is I don't have that much time this time to test, that's why I posted this in the forum to get some help on it beforehand.
In the time you waited for this post, you could have easily tested this. Once thing you will find is that if you are not willing to put in your own effort, you cannot expect others to put in more effort than you yourself are willing to expend.
0
