As I know, if you run PHP as a module for Apache is faster than running
as CGI. Also Python scripts can be run as a module(faster) or as CGI. The
main disadvantage for Python as a module is that you don't get all the
facilities of CGI.
--
PHP General Mailing List (http://www.php.net/)
To unsu
This is one of those questions that will get lot's of different answers
depending on your responders perspective. This is my view;
PHP can be executed as a CGI or as a MOD by Apache (or most web servers).
This means that Apache can load a fresh copy of PHP with each browser
request to the server
PHP comes in three major compilations: module, CGI, and CLI. The module
only works for web server (that I know of) and is the fastest way to
serve PHP based content from a web server. CGI can be run for either the
shell, or from the web server. There is a performance hit when run from
the web serve
* Thus wrote Scott Fletcher ([EMAIL PROTECTED]):
> Looked through all of those 11 README files and they don't say much about
> it.
Traditionally php had two modes:
1. module
2. cgi/commandline
the cgi/commandline could be used interchangably.
Now there are three modes:
1. module
2. cgi
Looked through all of those 11 README files and they don't say much about
it.
"Donald Tyler" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> PHP can be installed as either a CGI or an Apache module. There is
> documentation on this in the PHP readme files.
>
> Pretty much everything
PHP can be installed as either a CGI or an Apache module. There is
documentation on this in the PHP readme files.
Pretty much everything I read said that its always better to use the
Apache Module version. (apparently its much more stable and secure)
-Original Message-
From: Scott Fletche
John Taylor-Johnston wrote:
Three advantages I like:
1- no more cgiwrap.
2- thus I can work in any directory and am not bound to cgi-bin
'being bound to cgi-bin' is a function of how the server is set up, not
'cgi' itself. I've worked on systems where anything ending in .cgi
was treated as a cgi s
Three advantages I like:
1- no more cgiwrap.
2- thus I can work in any directory and am not bound to cgi-bin
3- Sheer ease of coding. A lot easier to learn, it's open-source and newsgroups are
more helpful. Perl groups are less helpful, programmer centred and not newbie-friendly.
Just my 2ยข
--
Mike --
...and then SpyProductions Support Team said...
%
% Does PHP use less system resources than CGI on a server?
Now that we know that by 'CGI' you mean 'perl' we're at least getting
*somewhere*. We don't really know what you mean, though, so I''ll see if
I can fill out the truth table for
Sorry, yes. :)
-Mike
> -Original Message-
> From: Leif K-Brooks [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 05, 2003 4:45 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [PHP] PHP vs. CGI
>
>
> CGI meaning perl?
>
>
CGI meaning perl?
SpyProductions Support Team wrote:
Does PHP use less system resources than CGI on a server?
I have a bulletin board which is incredibly active, but there is a PHP
sister to it.
Thanks,
-Mike
--
The above message is encrypted with double rot13 encoding. Any unauthorized
On 8/24/2001 10:54 AM this was written:
> I know this question has been asked many times before so I am not asking
> again :-) What I am asking is how I can search the forum, is there a web
> based system that I can use to search???
Well, there's a Newgroup:
news.php.net
There is an archive on
12 matches
Mail list logo
