Brad Wood wrote: >> >> Until proven otherwise I believe cfchart is just a symptom, sessions not >> being sticky in the connector is the cause. > > I have no doubt that the lack of sticky sessions is the cause. It just > doesn't seem that I should have to settle with Adobe telling me the > "correct" fix is simply to enable sticky sessions.
The way I see it there are three possible solutions to the abstract problem posed by cfchart being a 2-request tag: - subsequent requests need to be directed to the same instance; - instances share a common cfgraph cache; - all data for all graphs needs to be present everywhere all the time. The first 2 options are available to you and IMHO the third option has such horrible consequences for performance that I am glad they didn't implement it. Or do you see any other theoretical solutions? Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:273755 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
