Warnings awol in Win32 mod_perl.

sage appears twice as expected: first as a [warn], next as an [error]. So I shouldn't have a problem with LogLevel in httpd.conf, since warnings appear without a problem. How can I enable STDERR messages to appear in error.log in a Win32 environment? I would prefer not to introduce such hack

[mp2] PAR in production?

ndard" recommendation among the wise/experienced mp developers and admins? How have you, for instance, distributed your last application and how do you rate the experience? --Ali Isik

Re: Protecting source code

How about stunnix, folks, does anyone have any experience with their product? --Ali Isik On 8/23/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: On Aug 23, 2006, at 8:01 AM, Miha Lampret wrote: > Hello all, > > I am writting web application for mod_perl which will be installe

[mp2] insideOut mp.

Hi, folks, I need some mod_perl wisdom regarding the current situation with inside-out classes. I am trying to compare, in particular, the following two: Class::Std Object::InsideOut I can see that O::I has advantages in o thread safety o (at least partial) foreign-inheritance

Re: [mp2] repeatable segfault at ap_get_module_config

dPerl::Registry PerlOptions +ParseHeaders Options +ExecCGI PerlSwitches -wT #PerlTrace all CoreDumpDirectory /tmp == On 10/21/05, Philippe M. Chiasson <[EMAIL PROTECTED]> wrote: > Ali ISIK wrote: > > -8<

[mp2] repeatable segfault at ap_get_module_config

-8<-- Start Bug Report 8<-- 1. Problem Description: I am building a web application with a Postgres backend using Class::DBI. Some scripts generate repeatable Segmentation Faults on their second invocation. I tried compiling everything with cc and then com