mod_fcgid

Paul Querna, one of the reasons the Apache web server is still interesting, recommends mod_fcgid (“interesting” as in the retooling of authentication and the event mpm in Apache 2.2 is good stuff, and the RFC for a Perchild-like-MPM should be read by anyone who wants to do a modern web server that does mass virtual hosting).

So for mod_fcgid, he’s right.

I said the same thing about a year ago in various places and sites like Dan’s Hivelogic runs under mod_fcgid/Apache2 here.

We should actually look at rolling it out across all the servers, but I’m not sure it would overcome any file descriptor issues. It might.

For Rails it would just take replacing


AddHandler fastcgi-script .fcgi

with


AddHandler fcgid-script .fcgi

in the .htaccess file.

What’s the difference between this and the upcoming mod_proxy_fcgi, you ask?

The mod_proxy_fcgi just proxies or relays stuff from web server to an independently launched and managed fastcgi process (this is how we do strongspace’s fcgi by the way) while mod_fastcgi has a dynamic process manager: it can launch and control fastcgi processes.

mod_fcgid is better at dynamic fcgi process management than the original mod_fastcgi.

And then as the final bonus question, “how is litespeed’s handling of fastcgi different even from lighttpd and apache?” Hmm ….?

·:· Posted 2 January 2006, 11:54 by Jason Hoffman to Apache  |  

  1. The TxD blog is alive!!



    — Michael Ward    3 January 2006, 12:07    #
  2. BTW, we are planing on adding local process management to mod_proxy_fcgi, but we just haven’t gotten around to starting that part of the project yet.

    So, in the long term, mod_proxy_fcgi should replace this whole mess.

    — Paul Querna    5 January 2006, 16:05    #
  3. Great news Paul!

    — jason Hoffman    5 January 2006, 16:18    #