> -----Original Message-----
> From: Jean-Michel Hiver [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 26, 2001 9:18 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Apache::Registry HTTP HEAD "feature" fix ;-)
>
>
> > well, you should be subclassing Apache::RegistryNG instead of
> > Apache::Registry - then your method calls would work :)
>
> Sorry, Although I'm good at OO-Perl and CGI programming, I'm really
> quite new to mod_perl thus I really don't know what the xxxx I'm doing
> :-)
>
> What is the difference between Apache::Registry and
> Apache::RegistryNG ?
> (a simple RTFM followed by a URI would be welcome).
I believe that is in the perl.apache.org/guide
>
>
> > personally, I'm not too keen on a core patch that comes
> with "I don't
> > understand why... but it works" and this approach seems kinda kludgy
> > anyway...
>
> I totally agree, it's a horrible hack, and I'll be willing to provide
> something much better when I understand what's going on and why
> Apache::Registry seems to be reluctant to let its methods change ;-)
>
well, I just gave you a patch that worked :) basically, it only provides a
solution for mod_cgi compatible scripts, but if you're using the mod_perl
API then it is up to you to check $r->header_only and take appropriate
action...
--Geoff
