At 01:23 25.03.2002, Issac Goldstand wrote:
>>You must have taken this subroutine out of context. There are a certain
>>number of things which must appear for an Apache handler to work:
>>
>>package Apache::Whatever;
>>
>>You need to have that line to uniquely identify your module. If you use
>
>
> You must have taken this subroutine out of context. There are a
> certain number of things which must appear for an Apache handler to work:
>
> package Apache::Whatever;
>
> You need to have that line to uniquely identify your module. If you
> use the name Apache::Whatever, your handler must
At 17:30 23.03.2002 +, Jeff wrote:
>Just Curious of Hither Green writes:
>
>So, I am working my way through, and get to page 83 which has a little
>spellette:
>
>sub handler {
> my $r = shift;
> print STDERR $r->as_string();
> return OK;
>}
>
>looks easy peasy - but
>
>1) OK -> Bareword
>
> "OK" is a constant for the HTTP return code 200.
close. OK is 0, which is different from HTTP_OK which is 200.
--Geoff
Jeff wrote:
> Just Curious of Hither Green writes:
>
> I feel like a right tit for asking this...
>
> I already have mod_perl et al running, including my persistent DB connections
> etc etc, but following gourmet cookery advice on this list induced me to
> buy a copy of the mod_perl Dev
> 1) OK -> Bareword "OK" not allowed while "strict subs" in use
>well, that's easy to fix - I must be missing a 'use' [which one??]
>I assume OK is 1 - ie TRUE
"OK" is a constant for the HTTP return code 200. Add:
use Apache::Constants ':common';
to the top of your prog. and
Just Curious of Hither Green writes:
I feel like a right tit for asking this...
I already have mod_perl et al running, including my persistent DB
connections etc etc, but following gourmet cookery advice on this list
induced me to buy a copy of the mod_perl Developers Cookbook... and yes,
my na
