Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 07, 2013 05:20 AM by Angie xu - MSFT
Jan 31, 2013 04:22 AM|LINK
I'm attempting to get a PHP function to check if a user is logged into a ASP.NET site. From what I've read the SQL Server Session State mode would be perfect, becasue I could just have PHP check the database. The issue is that the site is several years old
and currenlty using the InProc session state. I have no training in .NET and was wondering if changing the Session State could cause any issues with the application or if there is a safe way to test this.
Thank you for your time.
Feb 07, 2013 05:20 AM|LINK
changing the Session State could cause any issues with the application or if there is a safe way to test this.
InProc state is considerably faster than either the state server or SQL Server session storage techniques. SQL Server and state server attribute their slowness to serialization/deserialization that happens while reading in/storing out the Session data from
the SQL/State server.
.However storing the session state InProc still has its own share of limitations.
- With each app domain restart Session state is lost;
- Process restart will result in loss of Session state data;
You could refer the usage of
In-Proc Session State Management, I think it will give some tips to you.
hope it helps you,