What's the philosophy behind the naming of InputMessageFilter and
InputBodyFilter, which seem to correspond to input connection filters
(ie for the headers) and input request filters (ie for the content).
Do you plan on a similar dichotomy for output filters? Not that I see a
need, but maybe
Oooops, whould have said InputFilterMessage and InputFilterBody...
- Barrie
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Fri, 11 May 2001, Geoffrey Young wrote:
it works fine against 1.3 mod_perl. I've been writing a test suite for
Apache::Dispatch consisting of a few different Locations and the like.
cool.
The only problem I was having was that I had to put
use lib qw(../blib/lib ../blib/arch);
in my
[EMAIL PROTECTED] (Doug MacEachern) wrote:
On Tue, 15 May 2001, Ken Williams wrote:
Is the suggestion below, about building Apache with -D_LARGEFILE_SOURCE,
accurate? That flag seemed to have no effect when I used it in building
Apache, and I couldn't find any mention of it in the Apache or
[EMAIL PROTECTED] (Doug MacEachern) wrote:
On Tue, 15 May 2001, Ken Williams wrote:
../gen_test_char test_char.h
env LD_RUN_PATH=/System/Library/Perl/darwin/CORE cc -c -I..
-I/System/Library/Perl/darwin/CORE -I../os/unix -I../include -DDARWIN
-DMOD_PERL
-DUSE_PERL_SSI -g -pipe -pipe
