How to track and eliminate session abuse?

Question

I am sure that in the past there were developers who brutally abused the state of my bad friend ASP.NET. The session would like to help keep track of things between requests, but can only do so much! Please help me relieve his pain so that he will happily work with us.

Does anyone know a tool that can control session sizes in multiple memory sessions? We are currently connecting IP affinity to the load ballaster because the sessions are so large that we want to keep them in memory. I want to be able to control both the average session size and the individual sessions that applications access them and what is stored in the session.

This heartless, uncontrolled abuse of session state should stop. Together we can find the answer.

Answer 1

I think you could implement something like this custom session provider and add some monitoring instead of zipping. This, of course, will make the session object larger and slower, but it can give you the necessary monitoring.

If you use SQL as the session provider, you can track it in sqlserver, but of course the sql server slows down session processing.

Answer 2

, . , .

, , , . (, )