Hey Dave, Thanks a lot for your response. Please see some comments inline below:
> Are you using clustering to support a larger number of users than a > single server? Or are you using it to provide failover in case a > server fails? Or both? The clustering is mainly for supporting a large number of users to route traffic to the less busy boxes. I think the failover you mention is also in place, but I don't think that's the primary reason for the cluster. > If the former, there's nothing wrong with using sticky sessions, and > you won't have to change your code. I'm hoping it's the former :) I guess that's what I'm getting at though... I'm sure you've done many applications that run on clustered servers, is using sticky sessions a common and accepted practice for using cfcs in a clustered environment? Or do larger applications like this just normally stick to the client scope and use the workarounds we've mentioned if they want to use persistent objects? I've worked at two shops with clustered servers and both just used client variables and did not have persisted cfcs. > I'm not sure where your userService object would live on a cluster of servers Shoot. For some reason I was thinking this would be the "easy part" in the sense that for some reason I was thinking the application scope would be available across all the machines and I could just store my singletons in the application scope. i.e. application.userService, application.securityService, etc. But now that I think about it, will this not work either in a clustered environment? Shoot, how do you guys solve this stuff? I must be missing something because this is the way I have learned to design applications... it can't be that it simply "doesn't hold up" when clustering is introduced, can it? > I'd probably just serialize objects, but I'd want to make sure that I'm not > storing > too much in these objects due to the overhead of this process. Hmm. So you are saying you would serialize objects that would typically be stored in the application and session scopes? But I need to be careful of storing too much in them... ? Shoot it sounds fragile, and I'm trying to introduce an updated code structure to the organization. I'd hate to bring some ideas in and then have it turn out that they are fragile or unworkable on a clustered server configuration. Thank you for any additional thoughts you are willing to share. Brian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:357085 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
