> have the form submit to a page with a hidden frame that keeps the session > variable alive.
If you have to, you can use a cookie/sql-backend combo as well, more complexity and development effort for more security and scalability. This is the method we implement. a explaination from builder.com.... "I recently read an article about maintaining session information on IIS using a COM+ object, and storing session information in SQL Server. The information was stored by generating a GUID for a user, storing that GUID as the identity of the user in a SQL database, and retrieving key-value pairs from that database by looking up the user's GUID. This GUID was stored as an HTTP cookie that was passed back and forth from the client to the server and vice-versa. This concept provides a method for storing session information on a Web farm apart from using session variables. (Background information: Session variables are unique to one server. So, on a Web farm, if a user requests a page from one server, and a subsequent request is sent to another server, the user loses his or her session data.)" To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
