I would like to take a poll from those who are using ASP.NET (IIS 5.0) cookieless Session management. It has been my experience that my Sessions are getting lost long before the expiration time. I am tempted to make my own Session management object using SQL Server (cookie-based session is simply not an option for the application I am developing).<BR><BR>What are the experiences with other developers and cookieless Session?I don't know the answer to your question. However, I do know of an article on Microsoft that might be helpful in setting up your own session management using SQL Server.<BR><BR>"Taming the Stateless Beast: Managing Session State Across Servers on a Web Farm"<BR><BR>http://www.msdnaa.net/interchange/preview.asp?PeerID=538While I don't know the reason either, I've been having the same trouble. There have been scattered posts throughout this board over the months pertaining to sessions randomly timing out. To date, I've not seen a solution.<BR><BR>])ryGreat minds think alike. I did use "Taming the Stateless Beast: Managing Session State Across Servers on a Web Farm" to build a Session management system a little over a year ago (COM+) which will not be difficult to port to VB.NET.Sessions usually time out for a couple reasons.<BR><BR>1) Something in the web.config,global.asax,or bin directory was modified.<BR><BR>2) Memory limits<BR><BR>3) Virus scanner fooling with config files.<BR><BR>I have not experienced any session problems, yet.<BR><BR>Shane3) Virus scanner fooling with config files.<BR><BR>Does this mean you do not have any type of active AV system on your server? This would not be an acceptable solution if so ...Just disable real-time scanning for that directory.
Cookieless Session is flaky
- Thread starter Hades
- Start date