Hi Leo --
From my experience, these are the questions that you should make sure
were asked first:
1. What is the effect on the user experience if the new server does not have the session information? 2. How large a memory footprint does each session occupy? 3. How often do session variables change? It has been my experience that session replication is almost never worth the trouble it causes in terms of extra load on network and webapps. Failure at the web app level usually has so little consequences that usually it is enough to simply: 1. just redirect the user to a new web server 2. the new server asks them to reauthenticate 3. looks for any work in progress that was significant enough to store in the database ( which the app is probably already doing as it is) 4. If it finds such work offers to take them back to that flow. Think about just storing every significant checkpoint in your app as a cookie that deserializes to a bookmark that takes them to an IExternalPage that will continue their work. You are using IExternalPage and bookmarks, right? right? (hint, hint) :-) -Pat --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
