Re: What if mod_perl is not an option?

There are a bunch of optimisations that can be made in the event that mod_perl is not an option;

Whether or not you are using these optimizations is orthonogal to whether you have mod_perl at your disposal or not. Lightweight pages are easier on both the server, the client, and the network in between regardless whether you use CGI or mod_perl. Eliminating redundant database connection is a good idea with both mod_perl and CGI. Static HTML is always faster, faster than mod_perl and faster than CGI.

Abigail

Comment on Re: What if mod_perl is not an option?

Replies are listed 'Best First'.
Re: What if mod_perl is not an option? by Coruscate (Sexton) on Feb 04, 2004 at 21:54 UTC
Eliminating redundant database connection is a good idea with both mod_perl and CGI. Are you suggesting that there exists a method of keeping pooled database connections from within a CGI, non-mod_perl environment? Or just saying that there should be as few (most likely one) database connection(s) per script instance?	[reply]
Re: What if mod_perl is not an option? by Abigail-II (Bishop) on Feb 04, 2004 at 22:22 UTC
Or just saying that there should be as few (most likely one) database connection(s) per script instance? Yes. Abigail	[reply]
Re: Re: What if mod_perl is not an option? by borisz (Canon) on Feb 04, 2004 at 22:06 UTC
As long, as you have the resources keep the connection to the database open. Apache::DBI does that for you. Boris	[reply]