I’m studying for a MS certification and one of the practice tests I’m doing has a question where the point of contention is the performance between storing the session in SQL Server as opposed to StateServer.
We store two objects in session. Somehow, one of the objects from another user got loaded into a different user’s session. The user should have had no access to this particular data, and as soon as they saw it they knew something was very wrong.
Before I start using Session State server for the benefit of making session state more robust in my apps compared to InProc state, I’d like to find a list of Pros and Cons for evaluation.
I have two identical applications setup on IIS on different virtual directories (I have done some workaround to ensure that they both have the same application name). Is there a way to share session id across two asp.net web applications?
I’m having trouble getting 2 identical ASP.NET MVC applications to share the same Session using a Session StateServer. The reason I’m trying to do this is we will eventually be deploying this app across 3 web servers that need to share the same state. We need to use StateServer because we are trying to minimise use of the db for non data-related storage.