"Patrice" wrote...
My personal preference wouldn't be to use GLOBAL.ASAX to workaround possible
issues with GLOBAL.ASA (IMO this will complicate the all thing plus I'm not
sure that session end is much more reliable, for example if you later switch
to the SQL provider for sessions it won't work at all).
GLOBAL.ASAX is significantly more reliable than GLOBAL.ASA when it comes to
Session_OnEnd. We ran some simple tests to prove it - try it yourself.
Your statement on the SQL provider is not applicable to our sitiation.
>
I would prefer much more to workaround the ASP issue I have with ASP alone.
For example you could :
- read the appropriate performance counter (possibly using a .NET assembly)
- keep track of session yourself without using the global.asa OnEnd event
(just register the last request date/time count for all sessions and count
those for which you had requests within the last "timeout" minutes, it could
be also a way to track if Session_end causes problem that is doing both and
comparing if you get the same value)
First of all, this is a hell of a lot of work to do when compared to using GLOBAL.ASAX,
which is a much more elegant, simple, and EFFICIENT solution. Right now, the site loads
lightening fast because we keep the code tight and optimized. Your solution generates
overhead that can be easily eliminated by using a GLOBAL.ASAX solution.
Second, your suggestion simply doesn't work. Remember, I have over 500 pages, including
some old legacy pages. Tracking all sessions would not be practical at all.
I appreciate your help, but if you don't know how to do what I want I'd rather you admit
that instead of trying to talk me out of doing it. I've been told that what I want to do
can be accomplished by a setting in IIS.
Victor
