Jan 18, 2012, 3:07 PM
I still think your best bet is to use httphandler to return only the data needed to render the chart. This is also good for separation of logic and UI. You can still render the chart control and set configurations on the server side but let the data handling be done via a httphandler. We do the same thing here. All the chart configs are handled on the server side. We have readonly session enabled on a ChartFactory.ashx. It works great because all the UI config code resides in one class and all the data loading is handled in the ChartFactory.ashx. If we ever decide to switch out the chart control (from Dundas to ExtJS 4), it will be easy. We have a desktop portal that's configurable with 1-3 columns and different widgets. User can choose from 10-15 widgets. Some are grids, some are charts, some are list of links. Data for grids and charts are all loaded with ChartFactory.ashx and GridFactory.ashx.
Edit: we also have drilldown capabilities in our charts by using Dundas's GetHtmlImageMap function.
Edit: we also have drilldown capabilities in our charts by using Dundas's GetHtmlImageMap function.