Thanks Perrin -- I tried this again and this worked but only after I changed from modperl to perl-script (which took a bit of time to figure out).
So, I wanted to conform to 'SetHandler modperl' for both style, consistent access to apache internals, and for optimizing general performance. I viewed this as one of our last steps to achieving better MP compliance. Specifically, In mod_perl 2.0 Server Configuration, I noticed the statement "with the modperl handler, you can gain even more performance." Can someone say where and relatively how much benefit can be derived by going that extra mile? I know some if it has to to with populating $ENV and other details. For me, it will require some but maybe not much re-factoring. Anyway, if someone has at least a good link to this detail or summary, that would be excellent and very much appreciated! Thanks again. On Dec 22, 2007 1:47 PM, Perrin Harkins <[EMAIL PROTECTED]> wrote: > On Dec 22, 2007 4:40 PM, Will Fould <[EMAIL PROTECTED]> wrote: > > "Global $r object is not available. Set:\n\tPerlOptions > +GlobalRequest\nin > > httpd.conf" > > And did you try what it says, i.e. setting PerlOptions +GlobalRequest? > > By the way, if you just call print() normally it should all be grabbed > by mod_perl anyway. Is there some reason you need to call $r->print() > instead? > > - Perrin >
