> -----Original Message----- > When you say cgi vs. php, I'm going to assume you mean cgi versus apache > module (correct me if I misunderstand). To be honest I don't know > enough about the internals of the apache module to tell you why it's > better for an apache server (would love it if someone could explain!).
PHP loads as an Apache module at startup and remains in memory, ready to process files. Running PHP as a cgi means that Apache has to load and run PHP each time a PHP file is processed. Basically, there's a lot of extra work in running PHP as a cgi. There are some benefits to having the cgi available though. For example, if you're at a unix prompt and need to process a file. Or, more commonly, if you want to execute scripts in cronjobs. -Ed -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
