Jeff Zhuk wrote:
...
Jeff,
whenever you send a message to the mod_perl list, I get a copy, because
I am subscribed to the list.
Then I get another copy, because you also send a copy to me directly.
So I get each message twice.
I guess it's the same for Randy.
It is not a real problem, but it is
On 8/23/07, Jeff Pang <[EMAIL PROTECTED]> wrote:
> why it need prototype in mp1's method handler?
Subroutine attributes did not exist before perl 5.6.
- Perrin
2007/8/24, Perrin Harkins <[EMAIL PROTECTED]>:
> On 8/21/07, Jeff Pang <[EMAIL PROTECTED]> wrote:
> > >PerlHandler Package::Name
> > >
> > >instead of:
> > >
> > >PerlHandler Package::Name->handler
> > >
> >
> > So on the first case,we need to write the handler as
> > sub handler { my $r = shift; .
On 8/23/07, Foo JH <[EMAIL PROTECTED]> wrote:
> I've read http://perldoc.perl.org/attributes.html about attributes, but
> it does not seem to suggest that tagging the method attribute to
> subroutine has any programming advantages, unless you're interested to
> list the subroutines with that attrib
Hello Perrin,
I'm interested in how you defined your handler with the 'method' attribute:
sub handler : method {
...
I've read http://perldoc.perl.org/attributes.html about attributes, but
it does not seem to suggest that tagging the method attribute to
subroutine has any programming advantage
On 8/21/07, Foo JH <[EMAIL PROTECTED]> wrote:
> Are there any technical advantages with either method, or is it a
> TIMTOWDI option given to the developers?
You can structure your code differently with method handlers, in ways
that appeal to some people. There's an example here:
http://modperlboo
On 8/21/07, Jeff Pang <[EMAIL PROTECTED]> wrote:
> >PerlHandler Package::Name
> >
> >instead of:
> >
> >PerlHandler Package::Name->handler
> >
>
> So on the first case,we need to write the handler as
> sub handler { my $r = shift; ...}
> because Apache may call the function directly as Package::Nam
-Original Message-
>From: Foo JH <[EMAIL PROTECTED]>
>Sent: Aug 22, 2007 11:15 AM
>To: Jeff Pang <[EMAIL PROTECTED]>
>Cc: Jordan McLain <[EMAIL PROTECTED]>, modperl@perl.apache.org
>Subject: Re: Internal Server Error
>
>
>> So on the first
So on the first case,we need to write the handler as
sub handler { my $r = shift; ...}
because Apache may call the function directly as Package::Name::handler.
on the second case,we write handler as,
sub handler { my $class = shift; my $r = shift; ... }
because '->' is a method calling.
Am I
-Original Message-
>From: Jordan McLain <[EMAIL PROTECTED]>
>Sent: Aug 22, 2007 10:52 AM
>To: modperl@perl.apache.org
>Subject: Re: Internal Server Error
>
>I might have solved my own problem...
>I was calling:
>
>PerlHandler Package::Name
>
>i
I might have solved my own problem...
I was calling:
PerlHandler Package::Name
instead of:
PerlHandler Package::Name->handler
although I am still confused as to why the first was working...
Jordan
On 8/21/07, Colin Wetherbee <[EMAIL PROTECTED]> wrote:
>
> Jeff Pang wrote:
> > Try change the c
Jeff Pang wrote:
Try change the codes to:
sub handler {
my $r = shift;
...
If his handler is called as a method, $class is an appropriate first
variable to shift out of @_. Using ($class, $r) = @_ is a perfectly
legitimate way of taking care of that.
Colin
On 8/21/07, Jordan McLain <[EMAIL PROTECTED]> wrote:
> sub handler ($$) {
> my ($class, $r) = @_;
>
> For some reason $r is not defined. This only happens intermittently... Does
> anyone have any ideas?
Sounds like sometimes it doesn't get properly called as a method, so
$r ends up as the
Try change the codes to:sub handler { my $r = shift; ...-Original Message-
From: Jordan McLain <[EMAIL PROTECTED]>
Sent: Aug 22, 2007 9:26 AM
To: mod_perl
Subject: Internal Server Error
Hello,I have a module that will fail every once in a while with the error_log message:Can't call
On Monday 05 March 2007 08:20, Viji ayyanar wrote:
> hai,
>I have encountered an error when i access the homepage. if possible give
> me the solution to resolve this problem . Thank You
> *The error is *
> **
>
> An internal server error occurred on http://localhost:8080/xdams:
>
> Date: 3/5/07
Stas Bekman wrote:
Arshavir Grigorian wrote:
Hello list,
I just tried searching for 'path_info' in the 2.0 docs and got an
internal server error(500).
http://perl.apache.org/search/swish.cgi?query=path_info&sbm=SecI&submit=search
The /x1/log/www/error_log says:
[Wed Nov 17 15:01:50 2004] [error
Arshavir Grigorian wrote:
Hello list,
I just tried searching for 'path_info' in the 2.0 docs and got an
internal server error(500).
http://perl.apache.org/search/swish.cgi?query=path_info&sbm=SecI&submit=search
The /x1/log/www/error_log says:
[Wed Nov 17 15:01:50 2004] [error] [client 65.92.240.
Thanks for your response. However at the moment what I needed was perl to work
on my webserver for testing purpose only on a global level. I found a way to
enable perl using an apache directive and bypassed mod_perl altogether. So for
the time being everything is fine. Thanks for you response
On Thu, 4 Nov 2004, Luke wrote:
> I have an intresting problem, I have a test server running windows 2k,
> Activestate perl and apache 2.
>
> I have loaded the perl module mod_perl.so as well as told it to use
> C:/Perl/bin/perlxx.dll.
>
> In the httpd.conf I have commented out the script alias
>
19 matches
Mail list logo
