Perl6 RFC Librarian wrote:
>
> =head1 ABSTRACT
>
> Perl is frequently used in CGI environments. It should be as easy to write
> CGI programs with perl as it is to write commandline text filters.
>
> =head1 DESCRIPTION
>
> Tom Christiansen proposed this in his perl6storm message:
>
> =item perl6storm #0025
>
> Make -T the default when operating in a CGI env. That is, taintmode.
> Will this kill us? Close to it. Tough. Insecurity through idiocy
> is a problem. Make them *add* a switch to make it insecure, like
> -U, if that's what they mean, to disable tainting instead.
>
> and this:
>
> =item perl6storm #0026
>
> Make CGI programming easier. Make as first class as
> @ARGV and %ENV for CGI progging.
For input variables, this would have the not-so-pleasant effect that
we'd have to upgrade perl to support changes of, or custom
implementations of, the CGI protocol (say, a different form encoding).
This may be survivable.
For output generation, it becomes worse. Support for new/different
output is quite common (witness the support for XHTML in current
CGI.pm), which is one reason which CGI.pm goes thorugh so many
revisions. I'd hate to upgrade the perl interpreter for such cases.
Now, implementing a more efficient version of CGI.pm is another matter.
I would hope that more efficient method calls, dropping some backwards
compatibility routines, and splitting the module into on-demand loaded
pieces would help.
Hildo
