There are a few ways to handle this. For one, you can set up your load balancing software/device to use 'sticky' or 'persistent' sessions, where a user is glued to the same server once he logs in. That's the easiest solution. The second way would be to run CFMX as a J2EE application in JRun or your J2EE application server of choice, and then configure the J2EE server to share J2EE session variables between the various CFMX applications.
Good luck, Eric On Thu, 6 Jan 2005 09:29:30 -0800, Benjamin Pate <[EMAIL PROTECTED]> wrote: > Hi.. > > I've avoided session variables since CF4 because it was so difficult > make them work on clustered servers. But, I have to admit that I've > never really looked in to how that has changed in the CFMX world. If > I started using session variables, what would I need to do to make > sure that the data would work properly in a clustered environment? > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email > to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' > in the message of the email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported > by Mindtool, Corporation (www.mindtool.com). > > An archive of the CFCDev list is available at > www.mail-archive.com/[email protected] > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
