On Jan 28, 2008, at 2:35 PM, Olaf van der Spek wrote:
On Jan 28, 2008 8:04 PM, Eric Covener <[EMAIL PROTECTED]> wrote:
On Jan 28, 2008 12:36 PM, Olaf van der Spek <[EMAIL PROTECTED]>
wrote:
On Jan 25, 2008 6:18 PM, Akins, Brian <[EMAIL PROTECTED]>
wrote:
On 1/24/08 3:14 PM, "Olaf van der Spek" <[EMAIL PROTECTED]>
wrote:
Working on making a FastCGI based setup the recommended approach
instead of mod_php is probably more important then async.
Actually,
it's a prerequisite.
Fastcgi is the "recommended way of using php and httpd 2, AFAIK.
Isn't it???
Where can I read about that recommendation?
I can't find it in the Apache or PHP manuals.
mod_php appears to be *the* solution.
http://www.php.net/manual/en/
faq.installation.php#faq.installation.apache2
"If you feel you have to use a threaded MPM, look at a FastCGI
configuration where PHP is running in its own memory space."
Is that what is meant by "Fastcgi is the "recommended way of using php
and httpd 2, AFAIK. Isn't it???"?
A single line seems a bit odd for the recommended approach.
Consider that, for many people, the main advantage of Apache2 over
Apache1 is the worker MPM. Also consider that a threaded MPM and
mod_php aren't a happy couple. If using prefork, mod_php works
just dandy... but for other reasons you'd likely want to
consider FastCGI anyway...
