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
> 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
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
> > 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
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
Nice! It all worked now. It's odd how the page said this problem would be
fixed in version 2.0 =)
Thanks for your help,
Nath
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Nath" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]
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
