in reply to Re: mod_perl and multiuser global variables
in thread mod_perl and multiuser global variables

hum... If it wasn't in the handler, than none of the code would execute (since it's all at the same level), and he'd see nothing at all (or rather a 500 HTTP error). I suspect he's using Apache::Registry, in which case the code *is* in the handler.

With Apache::Registry, the script gets converted to a function which is called every time the page is requested.

I bet the problem is in his hiGuiStatus module.

By the way rsennat, our isn't needed here. my will suffice and it would be a better choice here. The problem in the previous thread is that you were using a my variable as a global, which is a no-no in mod_perl. Here, they're not used as globals.

Replies are listed 'Best First'.
Re^3: mod_perl and multiuser global variables
by rsennat (Beadle) on Dec 05, 2005 at 15:35 UTC
    hi,
    i need this to be resolved. because there is no persistency in getting the logged in user's info.

    this code is in a separate .cgi file and not in a handler to execute from the browser, which will display the user's info.

    im using PerlResponseHandler ModPerl::RegistryPrefork in httpd.conf.

    Only in mod_perl i see this problem. Even in perl/cgi environment im using the module hiGuiStatus.pm, where there is no problem.

    thanks
    rsennat