On December 18, 2001 07:16 am, Chris Thompson wrote:
> the problem with this methodology
> using languages like Perl, PHP, etc. is that CGI implements a W3C-approved
> mechnanism for integration of External Gateway Programs - programs that
> provide a gateway between non-HTML information sources and the HTTP Web
> server. As such CGI is a powerful tool but it is extremely wasteful of
> server resources - every client request could require one or more
> additional process to be launched, plus the scripting language typically
> launches additional process. This proliferation of CGI process seriously
> limits the scalability of Web applications. Additionally CGI programs do
> not persist across client requests creating difficluties handling state
> information.

This is only correct if you are running PHP or Perl as a CGI program. Usually
one would use mod_perl or mod_php which do not launch extra processes. PHP
handles sessions extremely well, I don't know about Perl.

-Pete

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *