Re: Re: pulling content from db - is it a good idea?

The last option is particularly useful if the HTML page produced only changes once a day but the length of time that the script takes to run is long or consumes many resources.

An example would be if the web page showed a daily status report derived from a number of processor intensive SQL queries. The same script (using CGI and HTML::Template) can be scheduled to produce a fresh static HTML page on a daily basis.

inman

Comment on Re: Re: pulling content from db - is it a good idea?

Replies are listed 'Best First'.
Re: pulling content from db - is it a good idea? by Abigail-II (Bishop) on Nov 25, 2003 at 12:27 UTC
I'd say that even if the content changes every five minutes, it's in most cases worthwhile to generate a static HTML page every five minutes. About the only time where that's a bad idea is if all of the following are true: Generating the HTML page consumes a lot of resources. You get less than one hit on the index page every five minutes. The server is busy doing things other than serving the index page. Abigail	[reply]

Replies are listed 'Best First'.

Re: pulling content from db - is it a good idea?
by Abigail-II (Bishop) on Nov 25, 2003 at 12:27 UTC

Generating the HTML page consumes a lot of resources.
You get less than one hit on the index page every five minutes.
The server is busy doing things other than serving the index page.

Abigail

[reply]