The easiest way to render a chart is as a static image in one of several standard formats. This is appropriate for most purposes. However, if chart data changes frequently at the server, use binary streaming to efficiently store images.
When binary streaming is used, the chart image is sent directly to the client. When the browser requests the image of the chart, it does this in the same manner as when it requests a static image from the web server. This is particularly useful when the chart image is frequently modified at run time or when a web farm used.
When rendering a chart picture as an image, the chart picture is automatically saved to a file. The ImageLocation property determines the absolute or relative location and name of this file (see the figure below), and the file extension is automatically added, depending on the image type specified.
By managing the location and name of the file using the ImageLocation property, you can:
- Manage the maximum allowable number of image files that are generated.
- Insert a warning into the system event log if these temporary image files are overwritten within a specified length of time.
- Name files with a UID extension.