session & state

[link9]

Hello all --

Just discovered something I wasn't aware of concerning the state of session cookies.

I was under the impression that as long as some instance of a browser was open on your computer, then any session cookie that existed in that instance would be read by any other instance of the same browser. That is not exactly correct.

Here's how it works:

If you have a session cookie stored, and you open up another instance of the browser through the
file-->new-->window (CTRL-N) method, then the session will persist in the new instance.

However, if you click on the IE (or whatever) button from your desktop (or wherever) and open a new window that way, then it isn't persisted.

The difference is this:
The first method runs the browser in the same process. i.e. if you look at the number of processes running, the number won't change if you CTRL-N... still only one process of IEEXPLORER.EXE will be shown on the list.

However, if you click the button, then a new process is launched, you have two processes of the same program running, and the session cookie does not persist from one process to the other.

Might just play around with it to see what I'm talking about, but I found it interesting, so...

enjoy.
paul

 

[TheDrParker]

I have a page that mixes Javascript and VBScript. I do most of my coding in VBScript, but I have to do some in Java because the DTCs are written in Java.
My problem is that the Javascript seems to execute before everything else no matter where I put what. Is there any way to change this or get around it. I just need things to work in a certain order and the Javascript is executing way too early.

 

[TheDrParker]

Sorry about that last entry I don't know how it ended up there it was supposed to go into a new post. please ignore.