Session State: what's the best solution?


I have an (standard) ASP application using Session() vars to store UserIDs, UserName, UserACL, and so on...
This one suffers from all the well known ASP's handicaps handling Session State (web farms, IIS restarts...).

Moving to ASP.NET & C#, my question is: whats the best solution (performance, scallability...)?

Some sensitive data will be stored, so surviving IIS crashes is a must!

Please, take note: app. must suport multi-user simultaneous acess, i.e, on the same machine, the same user must be able to open, login (same or diferent credentials), and work with 2 or more diferent sessions (application instances), whitout mix up ID's or data...

Thanxs, in advance!
Who is Participating?
ihenryConnect With a Mentor Commented:
I believe his article is useful for you,
Set up the app to use SQL Server to handle sessions. Its the best solution for sessions if you can afford the minor performance hit on the machine.
LabDevAuthor Commented:
Thanxs a lot, both! Now i'm getting the right direction...

Stands old maxim: "Read a lot, before code a lot".....
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.