How Does Shared Session State in ASP.NET Web Applications Impact Accessibility?

Shared Session State: A Web Application Accessibility Bottleneck

This example demonstrates how shared session state in ASP.NET web applications can negatively impact accessibility. Two applications, /HRMS and /TravelDesk, utilize a shared session stored in SQL Server, configured as follows:

<code class="language-xml"><sessionstate allowcustomsqldatabase="true" compressionenabled="true" cookieless="false" mode="SQLServer" sqlconnectionstring="Application Name=Portal;data source=localhost;Initial Catalog=ASPState;User ID=sa;Password=dev2005" stateconnectionstring="tcpip=127.0.0.1:42424" timeout="720"/></code>

A user logged into /HRMS finds their session is also active in /TravelDesk when accessed via a separate browser window. However, a lengthy file upload within /TravelDesk locks the shared session in SQL Server, rendering /HRMS inaccessible during the upload process.

Resolution

The solution is straightforward: disable session state for the specific /TravelDesk page or handler responsible for the lengthy upload. This prevents session locking and maintains /HRMS responsiveness.

Additional Information

• Comprehensive Guide to Replacing ASP.NET Session State

The above is the detailed content of How Does Shared Session State in ASP.NET Web Applications Impact Accessibility?. For more information, please follow other related articles on the PHP Chinese website!