Bah, I can't believe I overlooked that. I completely forgot about the
continuous session vs. open/closed one. I just reset the hash to empty each
round to clean up its history.
Just like to thank you Perrin for your assistance. Much appreciated!
Cheers,
Nate
--
Report problems: http://perl
On Fri, 2004-03-12 at 14:29, Nath wrote:
> > It's a closure problem.
> - How do I fix that?
Pass your variables to your subs. Or use globals, but passing variables
to your subs is a good practice and you really should be doing it
anyway.
my $foo = some_sub();
bar($foo);
sub bar {
my $foo =
> It's a closure problem.
- How do I fix that? Is this something mod_perl does or apache does from
using mod_perl? If I switch back to standard perl, the problem doesn't
exist.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiqu
Thanks for the prompt reply. I used the ENV{MOD_PERL} as suggested -
actually printed out all of the ENV vars. No listing for MOD_PERL
except in the SERVER_SIGNATURE Apache/2.0.48 (Unix) mod_perl/1.99_13 Perl/v5.8.0
DAV/2 . So, I guess it's not really running yet.
Is the tag still need
On Fri, 2004-03-12 at 13:37, Nath wrote:
> This is odd since those older values should have been erased instead of
> being stored and reused again.
It's a closure problem. You have something that does this:
my $foo = some_sub();
sub bar {
print $foo;
}
The value printed for $foo will never
Yeah actually, that's what I just tried out and seems to be the problem.
Apparently when I query the string and break it up, the queries are being
stored for future use. When I printed out the query results each time, I
always get the same values:
First try:
http://www.nutty.ca/perl/index.cgi?page
On Fri, 2004-03-12 at 13:13, Nath wrote:
> > Sounds like client-side caching. Take a look at the headers you are
> > sending.
> - I'm not sure about this. How would the headers differ from using
> ActivePerl vs mod_perl?
>From using mod_cgi vs. using mod_perl. mod_cgi parses your headers and
add
> > There's just one more problem that seems to be lurking on my website. I
> > think this might have something to do with mod_perl's caching scheme.
>
> The first thing you need to understand is that mod_perl has no caching
> scheme. It is just perl and apache.
- My bad, I must have misread somet
On Fri, 2004-03-12 at 11:41, Nath wrote:
> There's just one more problem that seems to be lurking on my website. I
> think this might have something to do with mod_perl's caching scheme.
The first thing you need to understand is that mod_perl has no caching
scheme. It is just perl and apache.
Yo
There's just one more problem that seems to be lurking on my website. I
think this might have something to do with mod_perl's caching scheme.
Basically I have scripts like a photo album and calendar on my site. Both of
these scripts rely on information being passed via the URL header. So like
photo
Charlie Smith wrote:
In transitioning to mod_perl 1.99_13 I have a couple question. Today, I got
mod_perl built into Apache 2.
However, I would expect to be able to actually get the mod_perl working.
I used to be able to see if it was actually running by looking at the
GATEWAY_INTERFACE. (r
> What are the proper directives for replacing the following lines in the Apache
> 1.3.28 config file?
> PerlModule Apache
> PerlModule Apache::Registry
>
> I would assume something like:
> PerlModule ModPerl
you don't need that. but you might need
PerlModule Apache2
if you had an existing
In transitioning to mod_perl 1.99_13 I have a couple question. Today, I got
mod_perl built into Apache 2.
However, I would expect to be able to actually get the mod_perl working.
I used to be able to see if it was actually running by looking at the
GATEWAY_INTERFACE. (reference: to see GATE
>
Sent: Thursday, March 11, 2004 1:17 AM
Subject: Re: perl to modperl transition problems
> Nath wrote:
> > I loaded up modperl and everything looks like it's working, but there's
a
> > few transition problems moving over from perl to modperl. For starters,
the
> > &q
Nath wrote:
I loaded up modperl and everything looks like it's working, but there's a
few transition problems moving over from perl to modperl. For starters, the
"do" command isn't working. I use this to load external scripts since I keep
things separated into their own files. For some reason modpe
I loaded up modperl and everything looks like it's working, but there's a
few transition problems moving over from perl to modperl. For starters, the
"do" command isn't working. I use this to load external scripts since I keep
things separated into their own files. For some reason modperl just read
16 matches
Mail list logo
