Problems with the Perl/DBI/DBD Approach
The chain from browser to database is long.
Spawning a child process for each database operation.
Establishing a new TCP/IP connection every time (perhaps even doing a nameserver lookup).
Searching for and loading the DBI and DBD modules every time.
In MS environments, ODBC may be an issue.
Applications run in the server process rather than separately
Applications persist across requests rather than being created anew
Available as add-on modules for Apache, NCSA, Stronghold.
Integrated with Perl, Java, C, C++, and Tcl.
(commercial version of Apache) support
persistent DBI connections
Combines the Perl interpreter and the Apache server into a single executable
So -- does Perl become a webserver extension or does the webserver become a Perl extension? :-)
By Doug MacEachern
Available only with Apache
The Database Server Itself is Usually the Bottleneck
Other issues are likely less important.
Wednesday, 31-Oct-2001 14:17:36 CST
Copyright © 2006
Dan Keller Technical Services
4500 19th St., San Francisco
California, USA 94114
tel: 415 / 861-4500