Re: crummy build process for FastCGI-integrated Perl

Ray Zimmerman (
Tue, 18 Jun 1996 12:41:58 -0500

Message-Id: <v02120000adec97c08dfd@[]>
Date: Tue, 18 Jun 1996 12:41:58 -0500
From: (Ray Zimmerman)
Subject: Re: crummy build process for FastCGI-integrated Perl

Nigel Metheringham said (among other things):
>    Would it not be possible to:-
>      1. Just have an FCGI module, leaving the main perl stdio alone.
>      2. Have a modified CGI module which uses the FCGI input routines.
>      3. State that all output must go via a different file descriptor
>         which is handled by FCGI.  You could then attach STDOUT to that
>         descriptor at the top of the program if you wished.

... to which Mark Brown responded:

>Your suggestions are entirely reasonable.
>I have spent some time puzzling over the Perl documentation,
>trying to figure out how to provide my own implementation
>of the filehandle type, but haven't made much progress.  I'm
>quite willing to collaborate with a perlguts expert on doing
>the FastCGI-Perl integration right, but I don't think I have
>time to become a perlguts expert on my own.

I confess that I haven't looked at the fastcgi source code (I'm probably
not entirely qualified, to be honest) ... but I'm wondering, Mark, if
getting into the perlguts and implementing your own filehandle type is
necessary. With just a conceptual overview of how fastcgi works, it would
seem that it could be implemented almost entirely in Perl ... is this not
true?  I'd be curious to know why not?

|  Ray Zimmerman (   |  "The number you have       |
|  428-B Phillips Hall                |    dialed is imaginary.     |
|  Cornell Univ., Ithaca, NY  14853   |   Rotate phone 90 degrees   |
|  607-255-9645  Fax: 607-254-4565    |    and try again."          |