Inporc asp.net session state mode management Part 64 HD

Text version of the video http://csharp-video-tutorials.blogspot.com/2012/12/inporc-aspnet-session-state-mode.html Slides http://csharp-video-tutorials.blogspot.com/2013/08/part-64-inproc-session-state-mode.html All ASP .NET Text Articles http://csharp-video-tutorials.blogspot.com/p/free-aspnet-video-tutorial.html All ASP .NET Slides http://csharp-video-tutorials.blogspot.com/p/aspnet-slides.html All Dot Net and SQL Server Tutorials in English https://www.youtube.com/user/kudvenkat/playlists?view=1&sort=dd All Dot Net and SQL Server Tutorials in Arabic https://www.youtube.com/c/KudvenkatArabic/playlists Asp.net session state mode can have any of the following 4 values. Session state mode is set in web.config file. 1. Off - Disables session state for the entire application. 2. InProc - Will be discussed in this session. When the session state mode is set to InProc, the session state variables are stored on the web server memory inside the asp.net worker process. This is the default session state mode. Web Garden - Web application deployed on a server with multiple processors Web Farm - Web application deployed on multiple server Advantages of InProc session state mode: 1. Very easy to implement. All that is required is, to set, the session state mode=InProc in web.config file. 2. Will perform best because the session state memory is kept on the web server, within the ASP.NET worker process(w3wp.exe). 3. Suitable for web applications hosted on a single server. 4. Objects can be added without serialization Dis-advantages of InProc session state mode: 1. Session state data is lost, when the worker process or application pool is recycled. 2. Not suitable for web farms and web gardens. 3. Scalability could be an issue.