I know this has been discussed a little before, but the Test.pm
PerlHandler I've attached does not work as expected. The reason being
that dup-ing a read filehandle to STDIN overwrote STDOUT instead (well,
actually both, since apache apparently uses the same handle for
input and output).
hmm... i think i have a similar question.
i want to prevent people from writing data directly to the
apache connection and instead force them to use an object i
provide for generating output. they can call $obj-print()
directly, but i also want them to be able to use 'print
foo\n' as is
[EMAIL PROTECTED] (brian moseley) wrote:
hmm... i think i have a similar question.
i want to prevent people from writing data directly to the
apache connection and instead force them to use an object i
provide for generating output. they can call $obj-print()
directly, but i also want them to
