Re: Re: Re: Re: Re: New Session for new Window (or: Session ID vs. Process ID...)

[JayBonci]

There's not really any way to tell what windows are separate from each other. HTTP is a stateless protocol, and there's no way to tell from what window something was spawned. Netscape, Opera, IE, lynx et al all behave differently with regards to cookies and windows. There's really no good way to tell.

If I may ask, why would you want the Session to be different for each window?

    --jaybonci

[shushu]

I am the team leader of a product called FireBall-1, which is an internal CheckPoint tool for QA.
The report this tool is creating is an ASP built HTML files, with a complicated navigation within the report.
For example - if I use a loop in FireBall, I will see a loop in the report, and iterations of it.
The bottom line - we use the session to follow where the user is in the report.
But the user can open more then one report from the same IE window, and start his navigation. In this point I want him to get a session/cookie per window, in this is my current problem.

shushu

[JayBonci]

Why not track it by GET data from where he is in the application? It might be simpler to pass along that information in the link.

http://fireball/qa.asp?checkpoint=101&session=205.

If they jump out of that loop by opening a new window (or head to a spot where they couldn't possibly have gone to from the current report, create another session from there and change around all of the links (session=206, etc).

    --jaybonci

[shushu]

What is not clear to me is "create another session from there ..." - if I can create another session from any place, I should not have any problem.
From the example I gave it is clear that only one session exist, so in any case, even with your solution, I will still have one working session.
Am I wrong ?
shushu