The project I am currently working on involves MS SQL Server and ASP.net Web Services that use Session variables. Apparently this causes a client's calls to execute in a sequential manner. I want to make sure that these methods execute asynchronously.
After doing some research it appears to me the choicest method is to persist the session state in the database using a table that tracks sessions ( using guids say ) and separate tables for each session.
Before I dive directly into this I need to know if I can gain the same sense of asynchronous operations for the web service if I configure SQL Server to store the session.
Can I ?