- Original Message -
From: "Doug MacEachern" <[EMAIL PROTECTED]>
To: "Randy Kobes" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, April 23, 2001 11:04 PM
Subject: Re: win32 and apache_1.3.19
> On Mon, 23 Apr 2001, Randy Kobes wrote:
>
> >This patch also includes the t/TE
On Wed, 25 Apr 2001, Stas Bekman wrote:
> Exporter
> To void inherting B
> ...
> --
>
> Does it mean: Avoid using Exporter to void...?
that was a typo, s/void/avoid/
> also shouldn't:
>
> *import = \&Exporter::import;
> be:
> local *import = \&Exporter::import;
goodness no. fil
On Wed, 25 Apr 2001, Matt Sergeant wrote:
> I've no idea what makes the difference, I'm playing murder in the dark
> with these bugs :-)
:)
> But then I'm not using ModuleConfig any more either (I'm using a custom
> struct and custom XS code to get it).
ok.
> No, I don't have any other Loa
On Wed, 25 Apr 2001, Doug MacEachern wrote:
>
> > Well not quite. You had:
> >
> > BOOT:
> > XS_AxKit.name = "AxKit";
> > add_module(&XS_AxKit);
> > stash_mod_pointer("AxKit", &XS_AxKit);
>
> oh right. so is it the check for find_linked_module() that helps here or
> removing stash_mo
> Well not quite. You had:
>
> BOOT:
> XS_AxKit.name = "AxKit";
> add_module(&XS_AxKit);
> stash_mod_pointer("AxKit", &XS_AxKit);
oh right. so is it the check for find_linked_module() that helps here or
removing stash_mod_pointer() ? Apache::ModuleConfig->get won't work
without s
On Wed, 25 Apr 2001, Doug MacEachern wrote:
> hmm, that's how it was before the change in 1.25, i will revisit before
> 1.26.
Well not quite. You had:
BOOT:
XS_AxKit.name = "AxKit";
add_module(&XS_AxKit);
stash_mod_pointer("AxKit", &XS_AxKit);
void
END()
CODE:
remove_modul
hmm, that's how it was before the change in 1.25, i will revisit before
1.26.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This seems to work, Doug:
BOOT:
if (!ap_find_linked_module(ap_find_module_name(&XS_AxKit))) {
ap_add_module(&XS_AxKit);
}
void
END ()
CODE:
if (ap_find_linked_module(ap_find_module_name(&XS_AxKit))) {
ap_remove_module(&XS_AxKit);
}
--
/||
> "SB" == Stas Bekman <[EMAIL PROTECTED]> writes:
SB> Yup, Vivek is the godfather of this cool setup. At least I've learned
SB> about it from his pod!
Most of the ideas came from discussions on the mod-perl list; I can't
really take creadit for inventing them, just formalizing them and
writi
On Wed, 25 Apr 2001, Vivek Khera wrote:
> > "PC" == Paul Cotter <[EMAIL PROTECTED]> writes:
>
> >> > Another benefit of the front/back end setup is that the ligthweight
> >> > front-ends buffer the output from the heavy mod_perl processes,
> >> > freeing them up quickly to handle more request
> "PC" == Paul Cotter <[EMAIL PROTECTED]> writes:
>> > Another benefit of the front/back end setup is that the ligthweight
>> > front-ends buffer the output from the heavy mod_perl processes,
>> > freeing them up quickly to handle more requests. You don't want
>> > mod_perl talking directly
On Wed, 25 Apr 2001, Paul Cotter wrote:
>
> > >
> > > Another benefit of the front/back end setup is that the ligthweight
> > > front-ends buffer the output from the heavy mod_perl processes,
> > > freeing them up quickly to handle more requests. You don't want
> > > mod_perl talking directly to
> >
> > Another benefit of the front/back end setup is that the ligthweight
> > front-ends buffer the output from the heavy mod_perl processes,
> > freeing them up quickly to handle more requests. You don't want
> > mod_perl talking directly to slow clients.
>
Hi - Can you point me at a documen
Doug, I have a few questions regarding modperl_style.pod
=head2 Inheritance
=over 4
=item Avoid inherting from certain modules
Exporter
To void inherting B
...
--
Does it mean: Avoid using Exporter to void...?
also shouldn't:
*import = \&Exporter::import;
be:
local *import = \&
14 matches
Mail list logo
