Hello,

I was wondering if it was a good practice to, in the Session_End method, wrap up some loose ends. I want to check that certain work was updated against the SQL Server database when the user's session expired.

Does the Session_End ALWAYS trigger when the user logs off in the following scenarios:

- closes the browser
- navigates to a different page
- browser crash

Thanks,

Brian Mains

__________________
Brian

I have learned to never rely on session_end. It might work in .NET but it was always problematic in ASP. I don't know how IIS acts differently when it's running the .NET framework, if at all.

Navigating to a different page would certainly not cause session_end to fire because that would keep the session active. If anything the session_end would (should!) fire when the server times out the session. i don't think that any user action could result in that event. When you close the browser, it doesn't call the server and tell it "I'm done with the session." That's all up to the server.

Peter
------------------------------------------------------
Work smarter, not harder.