Re: crummy build process for FastCGI-integrated Perl

Ken Fox (kfox@ford.com)
Tue, 18 Jun 1996 16:03:52 -0400 (EDT)

Message-Id: <199606182003.AA11201@internet-mail.ford.com>
From: kfox@ford.com (Ken Fox)
Subject: Re: crummy build process for FastCGI-integrated Perl
To: mbrown@openmarket.com (Mark Brown)
Date: Tue, 18 Jun 1996 16:03:52 -0400 (EDT)
In-Reply-To: Mark Brown's message of "Tue, 18 Jun 1996 14:10:36 EDT"
             <199606181810.OAA23920@breckenridge.openmarket.com>


Mark Brown writes:

> The primary issue is that functions like print and printf are pretty
> darned fundamental to Perl.  If FastCGI doesn't implement a filehandle
> object, then FastCGI programs can't use these functions to write their
> output.  That makes FastCGI programs second-class citizens.

IMHO, it would be a lot better to have to call "FCGI::print" using a
standard Perl5 binary than to call "print" using a mangled Perl5 binary!

> (The existing filehandle object won't do because FastCGI needs to add
> protocol wrappers on the connection back to the Web server for output,
> and interpret the procotcol for input.)

Wouldn't it be possible to subclass FileHandle and get what you want?

- Ken

-- 
Ken Fox, kfox@ford.com, (313)59-44794
-------------------------------------------------------------------------
Ford Motor Company, Powertrain    | "Is this some sort of trick question
Analytical Powertrain Methods     |  or what?" -- Calvin
AP Environment Section            |