On 05 March 2003, Andrew Kuchling said:
> Those of you watching the quixote-checkins list will have noticed that
> I checked Hamish's classes into quixote.util today.  Various tweaks
> and changes were made while auditing the code; I'll try to get a beta3
> out in a day or two.

Oh good, thanks!

> I must confess I find the CGIScript class kind of unsettling.  The
> class uses the 2.2 'email' package, it changes sys.std{in,out} and
> then puts them back, and it modifies os.environ; all of this is kind
> of worrying.  There are no obviously visible holes, as far as I can
> tell, but all that fiddling around is potentially far-reaching.  Can
> running CGI scripts within Quixote be made to work?  Should we even be
> trying?

Finally glanced at the code, and I am totally and unequivocally OPPOSED
to the CGIScript class and all surrounding machinery.  Kill it.  Running
CGI scripts is the web server's job.

"Just because you *can* do something doesn't mean you *should*"

   -- Larry Wall (of all people)

--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org