The other clustering approach is to use Client scope rather than Session scope. To overly simplify things, Client scope is a contract between the user's browser and the application, whereas Session scope is a contract between the user's browser and the server. Since Client scope can maintain state with the application, a user can be seamlessly bounced from server to server without loss of data / connection. Works really well behind hardware load balancing, for example. Not so sure it fits your situation, but thought I'd at least mention it in case.
Just remember to never, ever use Registry as your Client scope store. It's the CF default, but it can quickly overwhelm server swapspace. Go ahead and use a datasource instead. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:314959 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
