SessionFarm is an Active Server Pages component that allows you to manage session state on multiple servers in a web-farm or cluster. SessionFarm utilizes the built-in IIS Session object which means you don’t have to learn new methods and objects. The IIS Session object is stored on either a file-share or a SQL database using optimized stored procedures.
ASP to ASP.NET integration
SessionFarm can help you migrate to ASP.NET a page at a time—add an ASP.NET page and access your existing session login variables or build new ASP.NET features into an existing ASP website.
SessionFarm allows you to access and update the old Session object’s variables from ASP.NET webforms. You can even start brand-new ASP sessions from with ASP.NET. For instance, you could rewrite your login system using ASP.NET, set the appropriate session variables and give access to your legacy ASP pages.
No Rewriting of Existing Code
You don’t have to rewrite any existing code that uses the built-in IIS Session object. SessionFarm saves and loads the IIS Session object automatically. When the object is instantiated the data from the file-share or SQL server is loaded into the built-in IIS Session. When the object gets destroyed (at the end of the page, when a ‘response.end’ or ‘response.redirect’ is issued) the IIS Session data is saved back to the file-share or database.
One Line of Code
One line of code added to each ASP page (perhaps via an include file) is often enough to get you up and running:
set SessionFarm = Server.CreateObject(“SessionFarm.SFSession”)
SessionFarm works by restoring and saving the built-in IIS Session object to a file-share or a back-end SQL server. The information stored on the file-share or SQL server is then accessible from all of the servers in your web-farm.
Download a free time-limited trial version and see if SessionFarm works for you.