Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <46CE4C54.1090104@extracktor.com>
Date: Fri, 24 Aug 2007 11:11:16 +0800
From: Foo JH <jhfoo-ml@extracktor.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Perrin Harkins <perrin@elem.com>
CC: modperl@perl.apache.org
Subject: Re: Internal Server Error
References: 
 <27950181.1187752308357.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
 <66887a3d0708231035n88a86c5p963cb7bc42b0e316@mail.gmail.com>
In-Reply-To: <66887a3d0708231035n88a86c5p963cb7bc42b0e316@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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 advantages, unless you're interested to 
list the subroutines with that attribute. But I suspect there's more to it.

Perhaps you can clue me in on this?

Perrin Harkins wrote:
> On 8/21/07, Jeff Pang <pangj@earthlink.net> 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::Name::handler.
>>
>> on the second case,we write handler as,
>> sub handler { my $class = shift; my $r = shift; ... }
>> because '->' is a method calling.
>>     
>
> For method handlers, you also have to declare it differently.
>
> In mod_perl 1:
> sub handler ($$) {
>
> In mod_perl 2:
> sub handler : method {
>
> - Perrin
>