Perhaps that is because the people that really use clustering do not depend on the rather limited options in the GUI but familiarize themselves with the underlying configuration options in JRun and the XML
files. To be honest, I didn't even know you could configure a cluster from the CF admin, I just set up the most basic cluster from the JRun admin and do the rest directly in the configuration files. ===== Apparently. Trust me, I do hope to eventually get to that point, but currently as I dive into clustering for the first time I am sticking to the GUIs for now until I feel a bit more comfortable with how everything works. *-*-*-*-*- > I suppose I expected there to be a more elegant BUILT-IN method for > working around this. Like what? We know how HTTP works. We know how HTML works. How could you possibly handle this even if those where the only 2 constraints? ===== 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. ~Brad ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:273787 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
