Menu
Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
ASP .Net
is session_end event totally USELESS?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Jason Shohet" data-source="post: 382973"><p>Hi Patrice. Thanks again for your comments, I really appreciate it.</p><p>In this case, if he goes to lunch it might be ok to return to the login</p><p>page, even though he doesn't request a page... its a timekeeping system and</p><p>we'll clearly explain that they are supposed to log out (not leave it</p><p>running).</p><p></p><p>Application_start is definately out since we have other code in there it</p><p>would conflict with. Application_beginRequest, I'm not sure what this is</p><p>(different than application_start?). I suppose the error page for the site</p><p>might be ok but won't that trap all errors? I want the user to see the</p><p>actual error screens (that tell me which line etc if something blows up),</p><p>I'd rather not mask it because if there's a legit error I want to see the</p><p>full error text. This is a case where we really don't have an 'error' per</p><p>se, just a redirect on session end.</p><p></p><p>I might try the way in my last posting first. We can also redirct the user</p><p>to a page that says "You were logged out because you left the application up</p><p>too long... click here to return to the login page..." and that might be</p><p>more user friendly. TY once again for your tips & help</p></blockquote><p></p>
[QUOTE="Jason Shohet, post: 382973"] Hi Patrice. Thanks again for your comments, I really appreciate it. In this case, if he goes to lunch it might be ok to return to the login page, even though he doesn't request a page... its a timekeeping system and we'll clearly explain that they are supposed to log out (not leave it running). Application_start is definately out since we have other code in there it would conflict with. Application_beginRequest, I'm not sure what this is (different than application_start?). I suppose the error page for the site might be ok but won't that trap all errors? I want the user to see the actual error screens (that tell me which line etc if something blows up), I'd rather not mask it because if there's a legit error I want to see the full error text. This is a case where we really don't have an 'error' per se, just a redirect on session end. I might try the way in my last posting first. We can also redirct the user to a page that says "You were logged out because you left the application up too long... click here to return to the login page..." and that might be more user friendly. TY once again for your tips & help [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
ASP .Net
is session_end event totally USELESS?
Top
