From: Chris W. <cw...@go...> - 2004-11-05 15:11:02
|
On Friday 05 November 2004 04:09 am, Chris McKay wrote: > Plus you need to write a file collector as well to tidy up the cache > directory ... > > C In my case, I don't need to delete a 'cache' folder, as it never grows beyond a set size of images. The image names are reused each time the graphs are created, so that static names can be used on web pages. It may not be the case for most people, but I have to generate my data from a database for each chart, and I have from 2 to 8 charts on a page, with my final result being a PDF of 30-40 pages. In my case, I think the cost of generating the graphs is high, with the individual graphs changing infrequently. I have used the servlet in an img tag before, and it appears that most people here like that method and recomend it first, but I have always liked the idea of reducing server load to the web server. If you have highly dynamic graphs, I guess you have no choice. I have also contemplated moveing the servlet graph generators to a seperate 'image' server, but decided that still would be best with more dynamic charts than I have. Mine only change when a user changes input data, not with an automatic process such as recording temperature data. All things said, if the servlet in an image tag is the preferred method of this list, I don't need to confuse new people by suggesting saving to a file again, but I did put thought into it before making my decision. Chris |