Re: re[2]: Debugging remotely with Apache2, FastCGI and Perl

On Thu, 2005-09-08 at 17:11 +0100, Shane De Jager wrote:
> Hi Sam,I'm
>  not sure quite what you mean. I very new at using FastCGI could you
> explain in a little more detail. Here is the configuration I have.
> 
> My httpd.conf
[...]
> Now how would I convert this to a FastCGIExternalServer? As you can
> see all I have done is change the handler for .pl scripts to FastCGI
> instead of CGI and I've modified the scripts to have a request loop.
> So for each script it will create a dynamic server. So do I have to
> make a external server for each script?

Sure, that's one option.

But normally, people will favour a single external server, and have a
script on the front that determines which of the real scripts should
handle the request.  I've had success wrapping multi-script wikis etc in
this manner before.  Best practice encourages a "single entry point" to
your "application framework" that dispatches to a per-request entry
point.  Application framework is often considered a dirty word, but is
necessary nonetheless for sanity.

It's a bit of a hurdle to get past, especially if you have a working
system that's been setup like this already, but ultimately makes it
easier to both debug the application, enhance security (as the web
server does not get involved in even starting the back-end process) and
potentially later, switch to other FastCGI compliant web servers that
are easier to configure and manage than Apache.

Sam.

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/