You could try a cookieless session.
By default ASP/ASP.NET uses a temporary cookie to handle session. The
behavior for windows used opened explicittely by the user is client side
depended (i.e. depends wether cookies are shared or not between those
windows).
A cookieless session (enabled in web.config) would likely allow to overcome
this problem (as the URL includes the information needed to establish the
session). A custom provider could also be a possible solution.
The exact scenario may help (you could have perhaps some other solution that
opening 3 browsers to point to these pages ?). For example when someone
needs to connect multiple times to the same application, I would see if it
could be built in in to the application (for application as in a mail
application that allows to have a mail box managed by those you'll add in an
access list).
--
Patrice
"Tarun Mistry" <no****@nospam.coma écrit dans le message de news:
%2****************@TK2MSFTNGP05.phx.gbl...
Hi guys,
thanks for the replies.
I'm unsure if im doing something wrong here, however I come from a PHP
background, here, PHP only writes 1 session per hostname/ipaddress.
In a php application, if I open 3 browsers pointing to a page session.php,
they will all contain reference to the same session. However if I open 3
browsers to session.aspx, they will all contain 3 different sessions. I am
trying to get functionality that is similar to PHP, is this possible?
Should I be looking at directly manipulating the cookie instead?
Thanks everyone.
Taz
