Session state and browser process

[Stefan]

Hello,

I am running .NET SQL Session state (V 1.1 blah blah) on a IIS6 server.

The problem is that my application spawns a new window via javascript
once the user logs in.

The user logs in on the main page and the info is stored in a session.

However, on some browsers, the act of opening a new window, creates
another session on the server and the last session (where the goodies
are) is lost to that window.

What can I do?

Stefan

 

[bruce barker \(sqlwork.com\)]

you could switch to cookieless sessions, or use a hybrid approach. use a
cookie for session management, but allow a sessionid in the querystring used
to open the new window, that overrides the cookie. this would require you
writing your own session manager, but its not hard.

-- bruce (sqlwork.com)

 

[Stefan]

Thanks Bruce,

but unfortuantley I can't use cookieless sessions states since I can't
pass stuff on the url (I am making AJAX like calls). I am thinking
that I will have to pass into each AJAX like call, a param being the
sessionID so I can recover the sessions (from my custom session DB).
I'll then scrap ASP.NET sessions altogether.

Thnks

Stefan

bruce barker (sqlwork.com) a écrit :

 

[Robbe Morris [C# MVP]]

"The problem is that my application spawns a new window via javascript
once the user logs in."

Is this really a good idea?

By the way, what browsers instantiate a new session by using
javascript window.Open(). I've never heard of a browser
doing that?

 

[Stefan]

Is this really a good idea?

I think it is; that is why I am doing it that way (strange question)

By the way, what browsers instantiate a new session by using
javascript window.Open(). I've never heard of a browser
doing that?

Explorer is doing it (but not on all computers, just some (great))

I too had never heard of this and didn't believe it, until I actually
saw it. Still I didn't believe it until I actually tested it several
times. Still don't want to believe it but it is fact

There must be a registery hack somewhere that forces explorer into a
new process (or just forcing a new sesison on the server somehow, I am
assuming explorer is in a new process, bcause it forces a new session
on the server. but I digress)

It is the strangest thing I have seen since the 'incident', (I have
never been able to play ping pong since)



Robbe Morris [C# MVP] a écrit :