in reply to Re: Re: New Session for new Window (or: Session ID vs. Process ID...)
in thread New Session for new Window (or: Session ID vs. Process ID...)

Instead of using the $Session object, use $Response->Cookie() and give it a value. What are you using the $Session object for depends on what you'd store in the ->Cookie (specific to your particular ASP application). This way, you can be gaurenteed that Session->Abandon() won't change your Session ID.

How are you authenticating the users? A database of some sort?

    --jaybonci
  • Comment on Re: Re: Re: New Session for new Window (or: Session ID vs. Process ID...)

Replies are listed 'Best First'.
Re: Re: Re: Re: New Session for new Window (or: Session ID vs. Process ID...)
by shushu (Scribe) on Feb 26, 2003 at 08:13 UTC
    My application is a strange one. I do not use the Session to authenticate anything, and I don't have any permission handling, since I don't need it.

    You wrote that by handling the $Response->Cookie I can force the $Session->Abandon to do nothing (by setting the cookie's Session ID key to the value I want - great).
    But - I want the opposite - I want to create a different Sessions per window.
    Before trying (which I will just going to do) I am almost certain that forcing a new Session ID in the Response->Cookie won't create a new cookie per window, and that I will still be with a Session per process.

    What do you think ?
    shushu
[reply]
      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
[reply]
        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
[reply]

In Section Seekers of Perl Wisdom