4
These three methods are used to clear session variables from the server,but the difference is
Session.Abandon includes Session.RemoveAll and also deletes the session id created for the session. So, subsequent request to .aspx page would create a new session with a new session id. Session.RemoveAll will remove all the user defined session variables but still keeps the session active.so if u want to end session you must use Session.Abandon().
Session.Clear() do the same job as Session.RemoveAll().
Session.Abandon includes Session.RemoveAll and also deletes the session id created for the session. So, subsequent request to .aspx page would create a new session with a new session id. Session.RemoveAll will remove all the user defined session variables but still keeps the session active.so if u want to end session you must use Session.Abandon().
Session.Clear() do the same job as Session.RemoveAll().
Hi Prajeesh,
How does IIS communicate at runtime with ASP.NET? Where is ASP.NET at runtime in IIS5? IIS6?
Please post a detail description .It will be usefull for all....
Thank you vinosh,i ll post it soon
HI,
I'm having a doubt. Does this Session.Adbadon() work as it claims in FireFox.
In my application when i'm using firefox eventhught i use the code Session.Abandon it does not clear the SessionID
Even though the session state expires after the indicated timeout period, the session ID
lasts as long as the browser session. What this implies is that the same session ID can
represent multiple sessions over time where the instance of the browser remain the same.
Post a Comment