> No idea I need to see more code to say what's going wrong there. Have
> you thought about using one of the session modules available from CPAN?
> e.g. http://search.cpan.org/~jbaker/Apache-Session-1.54/Session.pm where
> you can store sessions in MySQL, ...
Yes, I've been using Apache::Session::
On Wed, 2004-02-11 at 12:42, ian douglas wrote:
> Our real webapp.pl code is 25,000 lines long, I
> certainly didn't want to post that in a message ;o)
Okay, but it's much easier to help you if you post a real working
example. If you're still not sure how to solve the problem, post a
small workin
> To be blunt, this code has a lot of problems.
... and was written in 30 seconds to give an overview of what we *really* have.
It wasn't an actual snippet of the code we really use. The "defined in foo.pl"
comments were for readability for posting to the list, and yes, our cursors
really DO have
On Tue, 2004-02-10 at 21:13, ian douglas wrote:
> We have a 'base' script, which I'll call webapp.pl, which requires a number of
> other scripts, including a script that loads up a number of cursors for our
> database at startup so they don't get prepared over and over and over. The
> scoping of th
Please always also reply to the list.
No idea I need to see more code to say what's going wrong there. Have
you thought about using one of the session modules available from CPAN?
e.g. http://search.cpan.org/~jbaker/Apache-Session-1.54/Session.pm where
you can store sessions in MySQL, ...
Tom
O
Hi,
although that's more perl than mod_perl related I'd do the following:
1) make Perl-Modules out of e.g. mysql.pl e.g. MyModule::MySQLSupport
2) load them using use MyModule::MySQLSupport in webapp.pl which should
also be a Perl-Module under mod_perl e.g. MyModule::WebApp
3) When you are us
