how to avoid user from opening a new window

okie .... i will tell briefly what is the problem ....

Take a scenario wherein a user has logged into my application and he is performing a task which will put his user id and his employee id into the session. Then he opens another window by using either ctrl+n or through files->new window.

So now a new browser will open but the session will be same ..... in this newly opened browser, user performs some operation which will remove the user id and employee id from the session .... Now if he again comes back to the first window and tries to do some operation, then a null pointer exception will be thrown saying that the employee id is null .... because he has deleted that in the newly created browser ..... to avoid this situation what can we do ? can you please help me in this regard ? you got my problem right !!!

vinjavaa at 2007-7-29 17:29:39 >

Like Balus is saying, you have to divorce yourself from the idea that you are in control of the flow. You have to assume that objects in your session might not be there, and if you detect a situation where objects have been removed, you have to go back to a login page or restart at the beginning. It might not seem right from your perspective, but the user can't be too surprised, as it was the user that started a new window.

I stressed about this problem in one of my first web applications, and stored information on the session and compared that to info posted from each page, but that was way more trouble than it was worth. Insure with each server invocation that everything is in an acceptable state before processing.

jackett_dada at 2007-7-29 17:29:39 >