B
Bishop
I have a couple items I keep in session variables (using server memory) that
I can't pass across the address line. I've done everything I can find to
extend the sessions as long as possible but eventually the session will time
out. I didn't want to use SQL to hold my session information as this is a
single server enviroment with plenty of memory and I don't want to slow my
application down by waiting on SQL or have an additional dependency.
A new application I built uses the ASP.NET 2005 Login Controls. What I
noticed is that when I loose my session, I'm still logged in. I don't know
much about the login controls but assumed they were session based and would
vanish with my session.
So my question is, can anyone explain why I'm not loosing my login and how
it is being managed that it stays after my session is gone. Maybe I should
use another method such as SQL to manage my session information?
Thanks for any advice!
I can't pass across the address line. I've done everything I can find to
extend the sessions as long as possible but eventually the session will time
out. I didn't want to use SQL to hold my session information as this is a
single server enviroment with plenty of memory and I don't want to slow my
application down by waiting on SQL or have an additional dependency.
A new application I built uses the ASP.NET 2005 Login Controls. What I
noticed is that when I loose my session, I'm still logged in. I don't know
much about the login controls but assumed they were session based and would
vanish with my session.
So my question is, can anyone explain why I'm not loosing my login and how
it is being managed that it stays after my session is gone. Maybe I should
use another method such as SQL to manage my session information?
Thanks for any advice!