antivirus or a backup wont affect it either way unless they hinder the
session cookie being sent everytime...
okay you login page is not a frameset.. but the login page forwards it to
frameset... that causes a new session to be generated for the second
frame... i actually haven't monitored cause when i use session with frame...
i set those values from a particular frame and always access it in that
frame...
but enable tracing... add your custom attributes to trace.. monitor the
sessionid and the values... at some point.. you are doing something that is
causing server to open up a new session... see what's causing it... (plus
you are not losing the values... you are just opening and using another
session.. i.e. since its a different session you no longer have access to
other session's values... doesn't matter whether you read them or write to
them....
a better way to do it is not to use session specially for login page...
rather try using forms authentication... you need to do a few things... but
basic client info like username and userid can be bound to the
authentication ticket... and since you can access authenticationticket using
HttpContext.Current what session you are using doing matter...
hope this helps...
--
Regards,
HD
"Radu Colceriu" <ra***********@hotmail.com> wrote in message
news:eG**************@TK2MSFTNGP10.phx.gbl...
Hi,
thankx for the quick response.
The first page that is NOT in/a frameset (login.aspx) is opening the
sesion as far as I ca imagine and then this page will open the frameset. The
point is that it is working for a random period of time.... until something is
happend :) . The session variables are not altered by any one of the pages
from frameset.
I have no antivirus/backup running, I' using IE6.
-radix
"Hermit Dave" <he************@CAPS.AND.DOTS.hotmail.com> schrieb im
Newsbeitrag news:uF**************@tk2msftngp13.phx.gbl... mate... you are threading a thin line... the moment you have frameset..
with two frames you have two sessions on server...
cause each frame is a browser by itself having its own session...
so values set by frame1 in session would not be available to fram2 cause
it has its own session....
--
Regards,
HD
"Radu Colceriu" <ra***********@hotmail.com> wrote in message
news:e9**************@TK2MSFTNGP10.phx.gbl... HI,
I've an asp.net app like this:
login.aspx (no frame) :- save in session the user and pass
->
framedoc.html :- frameset 2 content
1. menu.aspx
2.docviewver.aspx
Everything work ok until at a random moment (1-5min) when the content
of some variables stored in the sesion is lost.
I'm not a big frameset fan but is a customer request :).
Do you have any ideea how can I fix this ?
Thanx,
-radix