You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Olaf van der Spek <ol...@gmail.com> on 2005/11/27 23:11:42 UTC
Any 'official' Apache FastCGI-like alternative planned?
Hi,
I've been wondering, do the Apache developers plan to develop and/or
include an official FastCGI-like module in Apache?
I know there's for example AJP but that appears to be aimed
specifically at Java.
An official module would be handy so that PHP can be run in separate
processes without requiring the http server itself to use separate
processes.
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Olaf van der Spek <ol...@gmail.com>.
On 11/27/05, Joshua Slive <jo...@slive.ca> wrote:
> Olaf van der Spek wrote:
> > Hi,
> >
> > I've been wondering, do the Apache developers plan to develop and/or
> > include an official FastCGI-like module in Apache?
> > I know there's for example AJP but that appears to be aimed
> > specifically at Java.
> >
> > An official module would be handy so that PHP can be run in separate
> > processes without requiring the http server itself to use separate
> > processes.
>
> You might be interested to read
> http://httpd.apache.org/docs/1.3/misc/FAQ.html#fastcgi
>
> I don't think the logic in that answer is set in stone. But that is the
> history of it.
With the latest update at http://www.fastcgi.com/dist/ being November
2003 I doubt that would still be an issue.
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Joshua Slive <jo...@slive.ca>.
Olaf van der Spek wrote:
> Hi,
>
> I've been wondering, do the Apache developers plan to develop and/or
> include an official FastCGI-like module in Apache?
> I know there's for example AJP but that appears to be aimed
> specifically at Java.
>
> An official module would be handy so that PHP can be run in separate
> processes without requiring the http server itself to use separate
> processes.
You might be interested to read
http://httpd.apache.org/docs/1.3/misc/FAQ.html#fastcgi
I don't think the logic in that answer is set in stone. But that is the
history of it.
Joshua.
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Olaf van der Spek <ol...@gmail.com>.
On 11/28/05, Nick Kew <ni...@webthing.com> wrote:
> On Sunday 27 November 2005 23:09, Olaf van der Spek wrote:
>
> > > Nope. There's the old mod_fastcgi and the more up-to-date mod_fcgid
> > > out there. Why does the world need another?
> >
> > But not in the official Apache distribution.
>
> How is that a problem?
It means the module is available on far less hosts. And with
non-dedicated hosts that's a significant issue (I think).
> > And not with a
> > Debian/DFSG-free license.
>
> Huh? If debian has taken to rejecting the GPL, what do they have left?
> Not the Linux or Hurd kernels, for starters.
Oops, I assumed you referred to the one from http://fastcgi.com/
> > KeepAliveTimeout is 15 by default. I guess/think the majority of
> > processes is idle during most (> 50%) of the time. I'm not sure, but
> > don't these idle processes still consume a lot of memory and
> > (persistent database connection) resources?
>
> Yep. Shifting that overhead to fastcgi doesn't get rid of it - unless
Why not?
Fastcgi isn't tied up during the keep alive idle time.
> (as I suggested) the PHP is a small proportion of total traffic, so the
> fastcgi can be a lot smaller than the main server. But then, the same
> applies to proxying another Apache instance.
>
> > A separate process would also allow you to run PHP with other user IDs
> > and process priorities/privileges and provide fault isolation (apache
> > process/connection doesn't crash when PHP does).
>
> Sounds like fastcgi will suit you nicely. I still don't see the problem.
No problem indeed if fastcgi is being used. I thought you were arguing
for just using the prefork mpm.
> (BTW, I sent the mod_fcgid maintainer a patch to build cleanly with
> Apache 2.1.8/9 a few weeks ago. Hopefully he'll review and apply it).
>
> > > running PHP as CGI, under fastcgi, or on a separate server instance
> > > running with prefork and proxied by the primary server?
> >
> > PHP as CGI causes too much overhead I think.
>
> That would depend on the volume of PHP usage.
Of course.
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Nick Kew <ni...@webthing.com>.
On Sunday 27 November 2005 23:09, Olaf van der Spek wrote:
> > Nope. There's the old mod_fastcgi and the more up-to-date mod_fcgid
> > out there. Why does the world need another?
>
> But not in the official Apache distribution.
How is that a problem?
> And not with a
> Debian/DFSG-free license.
Huh? If debian has taken to rejecting the GPL, what do they have left?
Not the Linux or Hurd kernels, for starters.
> KeepAliveTimeout is 15 by default. I guess/think the majority of
> processes is idle during most (> 50%) of the time. I'm not sure, but
> don't these idle processes still consume a lot of memory and
> (persistent database connection) resources?
Yep. Shifting that overhead to fastcgi doesn't get rid of it - unless
(as I suggested) the PHP is a small proportion of total traffic, so the
fastcgi can be a lot smaller than the main server. But then, the same
applies to proxying another Apache instance.
> A separate process would also allow you to run PHP with other user IDs
> and process priorities/privileges and provide fault isolation (apache
> process/connection doesn't crash when PHP does).
Sounds like fastcgi will suit you nicely. I still don't see the problem.
(BTW, I sent the mod_fcgid maintainer a patch to build cleanly with
Apache 2.1.8/9 a few weeks ago. Hopefully he'll review and apply it).
> > running PHP as CGI, under fastcgi, or on a separate server instance
> > running with prefork and proxied by the primary server?
>
> PHP as CGI causes too much overhead I think.
That would depend on the volume of PHP usage.
--
Nick Kew
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Paul Querna <ch...@force-elite.com>.
Olaf van der Spek wrote:
> On 11/27/05, Nick Kew <ni...@webthing.com> wrote:
>
>> On Sunday 27 November 2005 22:11, Olaf van der Spek wrote:
>>
>>> Hi,
>>>
>>> I've been wondering, do the Apache developers plan to develop and/or
>>> include an official FastCGI-like module in Apache?
>>>
>> Nope. There's the old mod_fastcgi and the more up-to-date mod_fcgid
>> out there. Why does the world need another?
>>
>
> But not in the official Apache distribution. And not with a
> Debian/DFSG-free license.
>
mod_fcgid? It is GPL.
You should really look at mod_fcigd:
http://fastcgi.coremail.cn/
I use it.
-Paul
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Olaf van der Spek <ol...@gmail.com>.
On 11/27/05, Nick Kew <ni...@webthing.com> wrote:
> On Sunday 27 November 2005 22:11, Olaf van der Spek wrote:
> > Hi,
> >
> > I've been wondering, do the Apache developers plan to develop and/or
> > include an official FastCGI-like module in Apache?
>
> Nope. There's the old mod_fastcgi and the more up-to-date mod_fcgid
> out there. Why does the world need another?
But not in the official Apache distribution. And not with a
Debian/DFSG-free license.
> If you have a specific need that the above don't meet, perhaps "FastCGI-like"
> isn't the best way to describe it.
>
> > I know there's for example AJP but that appears to be aimed
> > specifically at Java.
>
> AJP is part of the proxy framework. It's written by the java (tomcat) folks
> for their own use, but if you have a non-java AJP server, there's nothing
> to stop you using it for that.
>
> > An official module would be handy so that PHP can be run in separate
> > processes without requiring the http server itself to use separate
> > processes.
>
> I can't see how that's of much use except in the case of a server which
> uses a little PHP but mostly runs some application that benefits substantially
> from a threaded MPM. What would you need that isn't provided for by
KeepAliveTimeout is 15 by default. I guess/think the majority of
processes is idle during most (> 50%) of the time. I'm not sure, but
don't these idle processes still consume a lot of memory and
(persistent database connection) resources?
A separate process would also allow you to run PHP with other user IDs
and process priorities/privileges and provide fault isolation (apache
process/connection doesn't crash when PHP does).
> running PHP as CGI, under fastcgi, or on a separate server instance
> running with prefork and proxied by the primary server?
PHP as CGI causes too much overhead I think.
Proxying the entire server would be an option but a bit of overkill I think.
Re: Any 'official' Apache FastCGI-like alternative planned?
Posted by Nick Kew <ni...@webthing.com>.
On Sunday 27 November 2005 22:11, Olaf van der Spek wrote:
> Hi,
>
> I've been wondering, do the Apache developers plan to develop and/or
> include an official FastCGI-like module in Apache?
Nope. There's the old mod_fastcgi and the more up-to-date mod_fcgid
out there. Why does the world need another?
If you have a specific need that the above don't meet, perhaps "FastCGI-like"
isn't the best way to describe it.
> I know there's for example AJP but that appears to be aimed
> specifically at Java.
AJP is part of the proxy framework. It's written by the java (tomcat) folks
for their own use, but if you have a non-java AJP server, there's nothing
to stop you using it for that.
> An official module would be handy so that PHP can be run in separate
> processes without requiring the http server itself to use separate
> processes.
I can't see how that's of much use except in the case of a server which
uses a little PHP but mostly runs some application that benefits substantially
from a threaded MPM. What would you need that isn't provided for by
running PHP as CGI, under fastcgi, or on a separate server instance
running with prefork and proxied by the primary server?
BTW, this would be more appropriate to the users@ list.
--
Nick Kew