Session Variable Clarification

[CiberTHuG]

Okay... I have a question...

There is an ASP that lets you modify an employees contact info. You select the employee (say Joe) from a drop down box and click on a link and boom, you are in a form to update some stuff.

If you say "File -> New -> Window" in IE (and I'm sure the same in Netscape) then you now have two browsers open to the same modify employee page. Lets call these browser instance A and B.

Okay, go back in B. Select a different employee (say Bob). Change the information in A and submit. A will go back to the start page by default. If you look in the list of employee, there are now two Joes. The original one, and the one that just overwrote Bob.

The problem is, Session Variables. How can I set these up to limit themselves to just one instance of a browser and avoid this problem?

My immediate solution is to use hidden inputs instead of session variables.

[JoshT]

Sessions are based on Cookies, and as far as I know, web browsers will return the Cookie across different browser windows. It would have to be a client-config option...

[CiberTHuG]

Which means that I'll have to use the hidden inputs.

[monte96]

Just another reason to not use Session variables...

Keep your page stateless...

[idover]

well... here's a solution... as long as the user doesn't press F5 or Refresh as if that'll ever happen... but, after a few times, s/he will learn not to... lol...

' check for multiple clients with same session id
Session("clientCount") = Session("clientCount") + 1

If Session("clientCount") > 1 Then ' this window doesn't belong
	Response.Redirect "http://www.vbworld.com"
End If

i put it at the very top of the page... and it works fine for my scenario, except for when one refreshes the original window... maybe a hidden or querystring variable could be used to designate which window is the original window?... i'm going home... so good luck...