Apache-Filter
view release on metacpan or search on metacpan
Version: 1.024 Sat Sep 24 21:56:42 CDT 2005
- Fixed a bug that probably only I would ever see - when running the
"disttest" action, it was actually using the server configuration
from the top-level distribution directory, not the dist-dir
directory.
- For some reason all the files in the tarball of 1.023 looks like
they're read-only and non-executable, which causes lots of tests to
fail (e.g. those trying to execute CGI-style scripts). I'm
re-releasing what looks like correct permissions. [Spotted by Tom
Kirkpatrick]
Version: 1.023 Mon Jun 6 06:05:44 CDT 2005
- Fixed a testing bug under (certain versions of?) Mac OS X, in which
none of the pages in t/real.t would generate any output. [Peter
Farmer]
Version: 1.022 Fri Jan 31 14:00:48 CST 2003
in the chain is currently executing, and calling these routines out of
order messes up the counting.
* $r->deterministic(1|0);
As of version 0.07, the concept of a "deterministic" filter is
supported. A deterministic filter is one whose output is entirely
determined by the contents of its input file (whether the $r->filename
file or the output of another filter), and doesn't depend at all on
outside factors. For example, a filter that translates all its output to
upper-case is deterministic, but a filter that adds a date stamp to a
page, or looks things up in a database which may vary over time, is not.
Why is this a big deal? Let's say you have the following setup:
<Files ~ "\.boffo$">
SetHandler perl-script
PerlSetVar Filter On
PerlHandler Apache::FormatNumbers Apache::DoBigCalculation
# The above are fake modules, you get the idea
</Files>
lib/Apache/Filter.pm view on Meta::CPAN
crude counting method to figure out which handler in the chain is currently
executing, and calling these routines out of order messes up the counting.
=item * $r->deterministic(1|0);
As of version 0.07, the concept of a "deterministic" filter is supported. A
deterministic filter is one whose output is entirely determined by the contents
of its input file (whether the $r->filename file or the output of another filter),
and doesn't depend at all on outside factors. For example, a filter that translates
all its output to upper-case is deterministic, but a filter that adds a date
stamp to a page, or looks things up in a database which may vary over time, is not.
Why is this a big deal? Let's say you have the following setup:
<Files ~ "\.boffo$">
SetHandler perl-script
PerlSetVar Filter On
PerlHandler Apache::FormatNumbers Apache::DoBigCalculation
# The above are fake modules, you get the idea
</Files>
( run in 2.368 seconds using v1.01-cache-2.11-cpan-39bf76dae61 )