mod_perl 1.99_20 (2.0.0-RC3) is out:
http://perl.apache.org/dist/mod_perl-2.0.0-RC3.tar.gz
http://perl.apache.org/dist/mod_perl-2.0.0-RC3.tar.gz.asc (gpg sig)
CPAN:
file: $CPAN/authors/id/G/GO/GOZER/mod_perl-2.0.0-RC3.tar.gz
size: 1416964 bytes
md5: 395897082d4e026effcf0160838989e2
sha
The uploaded file
Apache-Test-1.19.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GO/GOZER/Apache-Test-1.19.tar.gz
size: 142015 bytes
md5: 795c1fcefd0f21b126f573fc46427139
Changes since 1.18:
Test for module.c instead of module.so for IfModule in
find_and_load_module [Chia-Liang
AvantGo (avantgo.com) is looking for a Senior Web Applications
Engineer. We use Mason and some custom Apache handlers in mod_perl.
There is also some C knowledge required, as well as MySQL (really any
semi-standard SQL) and of course Apache. The posting from the website
(http://www.avantgo.com/ca
> /usr/src/mp2/xs/APR/Base64/APR__Base64.h: In function
> `MPXS_apr_base64_encode':
> /usr/src/mp2/xs/APR/Base64/APR__Base64.h:37: static
> symbol `MPXS_apr_base64_enco de' is marked dllexport
>>>
Sorry, but I've never seen this kind of errors before. Any
chance
I was just doing the validation of my new program version when I have tried the
next
(simplified) code with firefox 0.92 which receives text and one image-upload
through a
formulary written correctly.
With Firefox all has run perfectly, then i've tested on internet explorer 6.0
and oh
surprise
On Wed, 5 Jan 2005, Ron Savage wrote:
> Server Version: Apache/2.0.50 (Win32) mod_perl/1.99_15-dev Perl/v5.8.4
[ ... ]
> After perl Makefile.PL I get:
> Can't locate Apache/Build.pm in @INC (@INC contains: lib
> C:/Perl/lib C:/Perl/site/lib .) at
> lib/Apache/TestConfig.pm line 33.
Hi Ron,
Jus
Randy Kobes wrote:
On Wed, 5 Jan 2005, Stas Bekman wrote:
Mike Carlton wrote:
[...]
But isn't there a problem with making db connections from startup.pl?
When the processes later fork, you potentially wind up with database
connection problems (I saw lots of problems under MP1 when I was doing
this
On Wed, 2005-01-05 at 14:58 -0600, Randy Kobes wrote:
> It's probably just me, but just to clarify the wording -
> are you saying the use of PerlChildInitHandler, as in
> Apache::DBI, *is* a safe way to to initiate database
> connections within a startup.pl?
It is, since it doesn't actually open a
On Wed, 5 Jan 2005, Frank Wiles wrote:
> Date: Wed, 5 Jan 2005 10:21:01 -0600
> From: Frank Wiles <[EMAIL PROTECTED]>
> To: Geoffrey Young <[EMAIL PROTECTED]>
> Cc: modperl@perl.apache.org
> Subject: Re: [summary] The Conflict of mp1 vs mp2 vs mp22 vs ... vs mpNN
>
> On Wed, 05 Jan 2005 10:50:3
On Wed, 5 Jan 2005, Stas Bekman wrote:
> Mike Carlton wrote:
> [...]
> > But isn't there a problem with making db connections from startup.pl?
> > When the processes later fork, you potentially wind up with database
> > connection problems (I saw lots of problems under MP1 when I was doing
> > thi
The mod_perl project has reached an important and exciting point in its
development cycle - the pending release of mod_perl 2.0, the first official
release of mod_perl designed specifically for Apache 2.0. Critical to the
success of this next generation of mod_perl is that it meets the needs of
t
On Wed, 05 Jan 2005 10:50:39 -0500
Geoffrey Young <[EMAIL PROTECTED]> wrote:
>
> > Admit it, Stas, The wheels have fallen off you nasty hack re
> > namespaces.
> > Stop trying to defend the indefensible.
> >
> > Just fix it!
>
> this kind of barb is really counterproductive, as have been many,
Thomas den Braber wrote:
The main module reloads without problems, most of the modules that are used
from the main module (with use) do not reload automatically.
That's the problem I am seeing
> Admit it, Stas, The wheels have fallen off you nasty hack re namespaces.
> Stop trying to defend the indefensible.
>
> Just fix it!
this kind of barb is really counterproductive, as have been many, many of
the remarks directed at Stas over the past two weeks. I can't imagine how
anyone would
I upgraded from 199_16 to 199_mod_perl-2.0.0-RC2-Xmas and found out that
Apache::Reload does not work the way it worked before.
I traced it back to the 199_17 version.
So in 199_16 everything worked fine, after 199_17 it did not.
I used the PerlSetVar ReloadDebug On in the apache.conf but nothing
Hi Folks
It gets worse :-(.
Apache::Test can't be upgraded...
Server Version: Apache/2.0.50 (Win32) mod_perl/1.99_15-dev Perl/v5.8.4
Apache::Test V 1.13 installed in the sane directory
/perl/site/lib/Apache/
Apache::Build V 0.01 installed in the pathological directory
/perl/site/lib/Apache2/Apac
Vincent Moneymaker wrote:
Stas Bekman wrote:
But you also indicated that all versions before 1.99_17 did work w/o
the package declaration, so that would be mean a behavior change.
First the results. I applied Philippe's patch, but no Reload messages
showed up in the error log when changes were m
17 matches
Mail list logo
