I hope the better answer would be ... In ASP model, the state maintenance is made by using separate processor/physical box by Serialization & Deserialization. Hence, IIS server reboot where the application is running does not affect the session server. So the user sessions at server can be taken back by the server.
Hi Mike, Thank you for your reply. But In sesson management there are methods like InProc, OutProc(SQL Server, Session State Server). As you suggested SQL server is the best way to maintain the session of the user especially for e-commerce applications. But my intension is how ASP engine can restore the user session, if we configure sessionstate mode with Sql Server/State server, when suddenly server reboots. I think, you can resolve my cenceptual problem. >> This site is designed well but there are so many bugs coming at runtime and also state is not well maintained.
I think you can only do this if you do your Session Persistence in Sql Server instead of as InProc. I believe this is an option in the web.config file.
sandeep talabathulaPosted Oct 24, 2009, 4:09 AM
In ASP model, the state maintenance is made by using separate processor/physical box by Serialization & Deserialization. Hence, IIS server reboot where the application is running does not affect the session server. So the user sessions at server can be taken back by the server.
sandeep talabathulaPosted Jan 24, 2008, 1:58 AM
Thank you for your reply.
But In sesson management there are methods like InProc, OutProc(SQL Server, Session State Server). As you suggested SQL server is the best way to maintain the session of the user especially for e-commerce applications.
But my intension is how ASP engine can restore the user session, if we configure sessionstate mode with Sql Server/State server, when suddenly server reboots.
I think, you can resolve my cenceptual problem.
>> This site is designed well but there are so many bugs coming at runtime and also state is not well maintained.
Mike GoldPosted Jan 23, 2008, 5:47 PM