Re: Complex session issue

session_name() enables you to refer to a session by name, rather than just referring to *a* session. check the manual, but I believe for session "x" you, would call session_name("mysession_y"); BEFORE session_start(), and for session y, you would call session_name("mysession_x"); there's a good example in the user-contributed notes of the manual Justin French on 16/07/02 4:01 PM, Divyank Turakhia (divyank.t@directi.com) wrote: > I have a situation where I have one browser window open for lets say web > application 'x'. Now I want my user to goto application 'y' on the same > domain in a new browser window by passing the authentication information > from application 'x' to application 'y'. I obviously donot want my > session variables to be continued in application 'y'. But at the same > time I donot want to destroy the session of my application 'x' > > Since they r in two COMPLETELY separate browser windows, both sessions > should logically be separate. But for some reason IE & netscape take a > new window in the same Instance. > > Is there any way I can open a new browser instance, such that the same > session is not continued and a new session in created leaving the old > session as it is? > > Or is there any other work around for the same? > > - Divyank > >