OK, so let's say it would only work with JRun. That is better than it not working AT ALL. What is the difference between Adobe telling me I am forced to enable sticky sessions if I intend to use cfchart in a cluster and Adobe telling me that I must use JRun if I intend to use cfchart in a cluster and don't want to enable sticky sessions?
My point is, at least that would be a solution for the majority of people (assuming the majority of people deploy on JRun). I would rather have a solution specific to JRun than no solution at all. In my opinion, that is what makes CF great-- out of the box functionality that "just works" without you having to jump through hoops. ~Brad -----Original Message----- From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Sent: Monday, March 26, 2007 4:20 PM To: CF-Talk Subject: Re: Targetting an instance Brad Wood wrote: > Well, since you asked, I would have expected there to be a setting you > could send in through the URL which would force the web server to hand > your request to a specific instance. > Then would expect an attribute of the cfchart tag called > forcesameinstance="true" or something which would generate a fully > qualified URL for the img src which specified the same instance which > was currently processing the cfchart tag. > That makes sense to me anyway. So how would that work if CF were deployed on a J2EE server that is not JRun? Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:273807 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
