note
Hero Zzyzzx
<p>I wouldn't say that FastCGI is dead. Stable, yes. Dead, no. It's been working beautifully on my Debian boxes for years, and is still supported in the new <a href="http://www.debian.org/releases/stable/">Sarge</a> that was just released. I believe the burgeoning <a href="http://www.rubyonrails.com">Ruby on Rails</a> community is picking it up, too, as one of the persistent mechanisms of choice. It just works, and darn well I might add.</p>
<p>One particularly thorny problem it helped me solve recently- I provide "boutique" hosting services for a <a href="http://www.plainblack.com/webgui">rather large perl-based CMS</a> that's under heavy development. I have clients that are on the stable branch and are happy where they are at, and clients that want to run the development "bleeding edge" branch. mod_perl makes this difficult because of namespace clashes, while with FastCGI I can run multiple long-running "instance scripts" and everything just works. And nicely, too.</p>
<p>You do lose the direct integration with the Apache API (I <b>love</b> mod_perl), but FastCGI is a very nice alternative persistent environment that's language independent.</p>
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-59531">
<p align="right"><font size=1 face="Verdana, San Serif"><b> -Any sufficiently advanced technology is<br> indistinguishable from doubletalk.</b></font></p>
<p align="right"><font size=1 face="Verdana, San Serif"><a href="http://www.geekuprising.com">My Biz</a></font></p>
</div></div>
464209
464305