Hi folks, I know that .Net has dropped the support for the session.OnEnd() event on global.asax because of scalability, distribution, bla bla bla.
The fact is that in some cases I cannot see how to manage the situation other than relying on Session.OnEnd(), for example in a real-life business app I am facing with these tasks on Session end:
- clear locks on records
- clean the temp directory where a large amount of files are generated (on-the-fly reports, etc)
and the big problem is when the user closes the browser without logging out. While I've thinked about a daemon that every X minutes purges the temp dir, with the complication of taking account of the creation date/time of the temp file, the same thing about record locking is more complicated.
Moreover, we are talking about applications that are replicated in a single machine over hundreds of databases and IIS sites, each with a differen temp folder and so on.
Thoughts?
What I have tried:
Considering this, we are sticking to .NET Framework for the moment.