Re: Checking for state's existence
Mark Aurit <[email protected]> Mon, 21 Apr 2008 07:18:18 -0700
| Newsgroups | gmane.comp.windows.devel.dotnet.web |
|---|---|
| Message-ID | <[email protected]> |
What exactly are you checking, and why? >>> Key values; for example the id of the person logged in which used throughout the app for audit logging. The "session" is normally handledautomatically by ASP.NET, and anything you add to the "session state" will > stay there until the session itself is torn down because of (for example) a > session timeout (person walks away for 20 minutes). You rarely need to check > explicitly for the "existence of a session" - if the session has expired, > the user will no longer be able to access restricted pages, for example. > (All this, of course, assumes you're using ASP.NET to manage session, state, > security, etc.) >>> Lets assume Im not. That if the session has expired the key value is gone and attempts to use it to log blow up. =================================== This list is hosted by DevelopMentorĀ® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com