On Sun, 19 Nov 2006, Issac Goldstand wrote:
Foo JH wrote:
Issac Goldstand wrote:
We were originally using 5.8.3, but reproduced the problem with both
activeperl 5.8.8.819 with mod_perl-2.0.3-dev (from your PPM repository)
as well as our own built perl + mod_perl 2.0.3-rc2
I wonder if modperl
We're using 2.2.3 - Upgrading everything to the latest stable versions
was the first thing we tried.
Issac
Foo JH wrote:
> Issac Goldstand wrote:
>> We were originally using 5.8.3, but reproduced the problem with both
>> activeperl 5.8.8.819 with mod_perl-2.0.3-dev (from your PPM repository)
>>
Issac Goldstand wrote:
We were originally using 5.8.3, but reproduced the problem with both
activeperl 5.8.8.819 with mod_perl-2.0.3-dev (from your PPM repository)
as well as our own built perl + mod_perl 2.0.3-rc2
I wonder if modperl on apache 2.2 will resolve this issue...
Jeff Pang wrote:
[error] Undefined subroutine
&Apache::ROOT::groups::listMembers_2epl::print_groupshow_head called at
/home/apache1.3/modperl/listMembers.pl line 26.\n
You're running into this problem:
http://perl.apache.org/docs/1.0/guide/porting.html#Name_collisions_with_Modules_and_libs
T
We were originally using 5.8.3, but reproduced the problem with both
activeperl 5.8.8.819 with mod_perl-2.0.3-dev (from your PPM repository)
as well as our own built perl + mod_perl 2.0.3-rc2
Randy Kobes wrote:
> On Sun, 19 Nov 2006, Foo JH wrote:
>
>> Issac Goldstand wrote:
>>> YES! While it's
On Sun, 19 Nov 2006, Foo JH wrote:
Issac Goldstand wrote:
YES! While it's acceptable for light and smallish applications, I've never
found it to be really usable once you're serving concurrent connections.
On that note, I have a contract (job) offer for anyone who knows their way
inside Per
This is a disappointing piece of news. Perl itself is very useful on the
Windows environment. If modperl cannot be reliably deployed on Windows,
how can we expect the Windows developers (which form the majority of
developers) to consider adopting perl/ modperl for the enterprise?
I hope we can
Why don't you post the error message here, and see if anyone has seen it
before?
Issac Goldstand wrote:
YES! While it's acceptable for light and smallish applications, I've
never found it to be really usable once you're serving concurrent
connections.
On that note, I have a contract (job) o
YES! While it's acceptable for light and smallish applications, I've
never found it to be really usable once you're serving concurrent
connections.
On that note, I have a contract (job) offer for anyone who knows their
way inside Perl (5.8) and mod_perl (2) enough to help troubleshoot a
win
