Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Yes, it will be slow. We realize that. Users wanted Google finance like charts which show historical data for last 35 years.. Google Finance charts are interactive too and that is what we are trying to replicate using silverlight.. Commented Feb 2, 2011 at 12:23
  • Still, you need to separate it. The SL-client is UI and holds/loads data at the user-scale. Commented Feb 2, 2011 at 12:31
  • 1
    @JohnC: But Google Finance charts are processed on the server. Install Firefox and Firebug and use Net tab to check amount of transfered data. I just browsed Broadcom Corporation and it works with 211KB of tranfered data. It dynamically requery (AJAX) the server if you zoom or scroll the graph - it works only with amout of data which are really displayed - btw. it is essential in any visualization. Commented Feb 2, 2011 at 12:49
  • 1
    In a case like this as the others mentioned, your WCF call should be to tell the server what you want to visualize. The server does the work and sends a result back. Most clients won't be able to handle a data set that large to do their own visualization, even if they could download it in a reasonable timespan (which they can't). Commented Feb 2, 2011 at 13:30