> -----Original Message-----
> From: Todd Finney [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 13, 2000 3:09 AM
> To: [EMAIL PROTECTED]
> Subject: Re: handler not quite doing what I expect
>
>
[snip]
>
> My other question is about Apache::Request. Why does this:
>
> my $apr = Apache::Request->new($r);
> my @params = $apr->param;
>
> poon the parameters listing when it runs? If I have a page
> that contains
> three scripts as components, I need every component to get
> any arguments
> passed in. If I run the above for each component, only the
> first one gets
> the arguments. All others after that get junk. I have
> corrected for
> this by calling the code only once, but I'm curious as to
> whether or not
> this is the expected behavior and why.
yes, the behavior is expected :)
try Apache::RequestNotes - it uses Apache::Request during init so everyone
can get to the data as many times as they want.
HTH
--Geoff
>
> thanks everyone,
> Todd
>
>
>
>
>
> At 02:49 PM 9/12/00 -0400, Todd Finney wrote:
> >Hi,
> >
> >I have a handler - we talked about it a few weeks ago,
> Templating Redux -
> >that mostly works. It takes any page request, and wraps it
> in a template
> >file while also adding some cookie-defined components to the
> >template. One of the problems it is having is when I try to
> insert a cgi
> >script as anything other than the requested page (as a toolbar for
> >example), the server tries to execute the content file,
> which is usually
> >an html file. If the content is a perl script, and the components
> >(toolbar, etc) are static, everything works peachily.
> >
> >The wrapper follows. Code comments that could lead to my
> improvement as a
> >(mod_)perl programmer are always most welcome. If you need more
> >information, please ask.
> >
> >thanks everyone!
> >Todd
> >
>
