Well, I got mod_perl installed & tested as recommended in
modperl_dev.pod, and I thought I'd try to make it a little easier for
others. I'm not sure if I've overlooked something that would have made
it easier for me, however, and I presonally can't say why I think 5.6.1
won't cut it, I'm passing o
Are there any plans to fire up a perl interpreter at httpd -t time,
perhaps with an implied addition of -c to PerlSwitches?
I'm looking for cheap and easy ways to test Perl code without
killing/launching a server.
FWIW, I started down this trail because I have a button mapped to "perl
-cw %" in
On Thu, May 03, 2001 at 02:44:50PM -0700, Doug MacEachern wrote:
> On Thu, 3 May 2001, barries wrote:
>
> > I'm looking for cheap and easy ways to test Perl code without
> > killing/launching a server.
>
> you're talking 2.0, right?
Yup.
> it will b
->read(my $buffer, 1024)) {
$filter->print(lc $buffer);
}
0;
}
doesn't print the same mtime twice:
/home/barries/2.0/www/htdocs/index.html.en
988998777
952717376
Fri May 4 13:52:57 2001
Fri Mar 10 14:42:56 2000
...snip...
- Barrie
[barr
On Fri, May 04, 2001 at 02:21:25PM -0700, Doug MacEachern wrote:
> > Running glibc-2.1.3 on va-linux's
> > tweaked RedHat 6.2, FWIW. Typical gdb-5.0 session below, the 19941004
> > gdb that came installed on his box behaves similarly.
>
> it looks fine to me, what is the problem exactly?
Sorry,
[cross-posting to new-httpd, since that's the more appropriate forum]
Background: I had trouble single-stepping through the routine defined by
AP_IMPLEMENT_HOOK_RUN_ALL(int,pre_connection,(conn_rec *c),(c),OK,DECLINED)
.
On Fri, May 04, 2001 at 02:21:25PM -0700, Doug MacEachern wrote:
>
>
On Fri, May 11, 2001 at 08:07:18AM -, [EMAIL PROTECTED] wrote:
>
> % cd httpd-2.0
> % cvs up -dP
> + % cd srclib/apr
> + % cvs up -dP
> + % cd ../..
> + % cd srclib/apr-util
> + % cvs up -dP
> + % cd ../..
I always thought the first cvsup would do the other two. Which
On Fri, May 11, 2001 at 07:45:55AM -0400, Geoffrey Young wrote:
>
> > sub MY::test {
> > return Apache::TestMM->test if eval { require Apache::TestMM };
> >
> > return <<'EOF';
> > test:
> > @echo This test suite requires Apache::Test
> > @echo available from the mod_perl
On Fri, May 11, 2001 at 08:36:56PM +0800, Stas Bekman wrote:
> On Fri, 11 May 2001, barries wrote:
>
> Now I've tried it at home, and I didn't need to run 'cvs up' in srclib
> subdirs... this is on Mandrake 8.0 (cvs-1.11-5mdk) versus Mandrake 7.2
> (cvs-1
On Thu, May 10, 2001 at 08:37:38PM -0700, Roy T. Fielding wrote:
>
> Yes, that is the standard "reasonable default" per the Gnu project's
> makefile standards, which is why autoconf sets it. As you discovered,
> it can be overridden by setting any value for CFLAGS prior to running
> configure.
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 I'm
Oooops, whould have said InputFilterMessage and InputFilterBody...
- Barrie
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Wed, May 16, 2001 at 08:15:50PM -0700, Doug MacEachern wrote:
> On Wed, 16 May 2001, barries wrote:
>
> > What's the philosophy behind the naming of InputMessageFilter and
> > InputBodyFilter, which seem to correspond to input connection filters
> > (ie for t
The current output filters implementation sends an EOS before the Perl
handler exists, cutting off trailing output from a filter like:
sub handler {
$f = shift ;
$c = 0 ;
while ( $f->read( my $buffer ) ) {
$c += length $buffer ;
$r->print( $buffer ) ;
On Tue, May 22, 2001 at 11:33:58AM -0400, barries wrote:
> The current output filters implementation sends an EOS before the Perl
> handler exists, cutting off trailing output from a filter like:
s/exists/exits/. Anyway, this is probably a broken patch, since it
assumes the first bucket b
On Tue, May 22, 2001 at 10:56:42AM -0700, [EMAIL PROTECTED] wrote:
> as i mentioned before, there will be a Perl api that provides the
> functionality/control of the C api.
Not trying to make you repeat yourself, just seeing if I'm thinking
remotely sanely about the issues.
> will probably also
On Tue, May 22, 2001 at 03:14:35PM -0700, Doug MacEachern wrote:
> i read on new-httpd that we do not need to send a eos bucket at all and
> apache will do the right thing.
I think Ryan is means that's true only for response handlers.
ap_finalize_request_protocol() sends an EOS if one hasn't been
Here's a quick hack that exposes a PerlFilter per-server command that
ap_register_output_filter()s whatever name(s) are provided them with a
cobbled-together modperl_perl_filter_handler().
I can now enable a Perl filter using SetOutputFilter or in a
PerlFixupHandler (in lieue of a PerlFilterRegis
On Thu, May 24, 2001 at 05:52:39PM -0700, Doug MacEachern wrote:
> let's consider everything before adding new code.
Ok :-). I have a reply in queue that works through your ideation w/
questions & suggestions. But first, let's look at really bifurcating
the API into a Perl*Filter API and a more
Background: A couple of yuears ago I wrote a complete Perl input/output
filtering system much like the current Apache filter system and a bunch
of filters for it. I'm hoping to port it to mod_perl-2.0 and let
mod_perl do the heavy lifting (filters are just a pain to manage).
Having done a bunch o
On Fri, May 25, 2001 at 11:06:47AM -0700, Doug MacEachern wrote:
>
> i think we're on the same page, this is pretty much the same as what
> i outlined under 'direct C api mapping.
Ok, I think I was underestimating how much padding you wanted on the
direct C API mapping. I thought that that woul
On Fri, May 25, 2001 at 11:37:01AM -0700, Doug MacEachern wrote:
>
> i think we should focus on getting the rest of the direct C api
> mapping done, which we want in any case. with that in place, you
> should be able to prototype the approach you outlined here as a pure
> Perl module.
Yeah, I
On Fri, May 25, 2001 at 02:31:38PM -0700, Doug MacEachern wrote:
> On Fri, 25 May 2001, barries wrote:
>
> > I think that two things are necessary to enable a pure Perl
> > implementation:
> >- adding is_BOS() and is_EOS() to Apache::Filter (or to
> >
On Fri, May 25, 2001 at 03:52:31PM -0700, Doug MacEachern wrote:
> On Fri, 25 May 2001, barries wrote:
>
> > We're on the same page, but right now $ctx in the $r->add_xxx_filter(
> > "foo", $ctx) is written to the f->ctx field that the modperl_filter_t
&g
On Fri, May 25, 2001 at 06:30:03PM -0700, Doug MacEachern wrote:
> On Fri, 25 May 2001, barries wrote:
>
> >Apache::ap_add_output_filter( "foo", AP_FTYPE_CONTENT, $ctx )
>
> you mean ${r,c}->add_output_filter("foo", $ctx), right?
Yeah. Getting
Since you've done the tieing STDIN/STDOUT bit in the past (1.x), why not
tie STDIN and STDOUT in modperl_output_filter_handler()? That would make
filter sub code bit less funky:
sub handler {
while (<>) {
print uc ;
}
}
STDIN/STDOUT would then be restored to their
On Sun, May 27, 2001 at 01:11:25PM -0700, [EMAIL PROTECTED] wrote:
> On Sun, 27 May 2001, barries wrote:
>
> > STDIN/STDOUT would then be restored to their original state (tied or
> > untied) up exit?
>
> there are Apache::Filter::{TIEHANDLE,PRINT} methods, the tie jus
I know you don't need *FunctionTable.pm, but hey, it's free.
--- ../modperl-2.0/src/modules/perl/modperl_filter.hTue May 22 11:07:28 2001
+++ src/modules/perl/modperl_filter.h Tue May 29 14:16:26 2001
@@ -42,6 +42,15 @@
SV *buffer,
I tripped over the fact that the PerlResponseHandler does not send EOS
(which is optional, after all). Here are a couple of reasons mod_perl
should go ahead and send the EOS right after the PerlRespnseHandler
exits:
- Efficiency: one less brigade & associated calls, since it can be added
to th
On Wed, May 30, 2001 at 03:40:36PM -0700, Doug MacEachern wrote:
> On Tue, 29 May 2001, barries wrote:
>
> > I know you don't need *FunctionTable.pm, but hey, it's free.
>
> we do need the ModPerl::FunctionTable entries.
I meant that I should probably omit Functi
On Sun, Jul 15, 2001 at 10:33:50PM -, [EMAIL PROTECTED] wrote:
> +static int modperl_filter_register_request(request_rec *r,
> +if (*name == 'M' && strEQ(name, name)) {
strEQ(name, name)?
> -#define MP_INPUT_FILTER_MESSAGE 0x01
> -#define MP_INPUT_FILTER_BODY0x
31 matches
Mail list logo
