On 17-Sep-04, at 7:36 PM, Stas Bekman wrote:
and if you can send the missing tests and docs that will ensure that
your patch will be committed promptly.
As I can see src/docs/2.0/user/config/config.pod's PerlSetVar entry is
completely empty :( So it needs to be ported from the mp1 docs first
an
[Geoff, please don't cross-post the thread, Rici is not subscribed and
it'll be just confusing as half of the posts won't make it to the dev list]
Rici Lake wrote:
On 17-Sep-04, at 4:55 PM, Stas Bekman wrote:
I'd rather not add new directives, but have:
On reflection, I think I agree. It is poss
Sorry -- the APR patch for OpenBSD _did_ make it into the APR that is
tagged for release with 2.0.51.
http://cvs.apache.org/viewcvs.cgi/apr/build/apr_hints.m4?rev=1.53.2.9&only_with_tag=APACHE_2_0_51&view=auto:
...
*-openbsd*)
APR_ADDTO(CPPFLAGS, [-D_POSIX_THREADS])
# binding
> So is that the right skip rule (hoping that 2.0.52 will fix NetBSD:
>
> my $should_skip =
> ($^0 eq /^OpenBSD$/i && !need_min_apache_version('2.0.51')) ||
> ($^0 eq /^NetBSD$/i && !need_min_apache_version('2.0.52'));
>
> and the tests that need to be skipped are:
>
> t/filter/both_str
On 17-Sep-04, at 4:55 PM, Stas Bekman wrote:
I'd rather not add new directives, but have:
On reflection, I think I agree. It is possible to achieve virtually
the same effect with
PerlSetVar foo ""
So I trimmed a few lines out of the patch, ran the tests again, and
this time I will cut and paste i
Ken Simpson wrote:
Sorry -- the APR patch for OpenBSD _did_ make it into the APR that is
tagged for release with 2.0.51.
http://cvs.apache.org/viewcvs.cgi/apr/build/apr_hints.m4?rev=1.53.2.9&only_with_tag=APACHE_2_0_51&view=auto:
...
*-openbsd*)
APR_ADDTO(CPPFLAGS, [-D_POSIX_THREADS])
Joe Orton wrote:
On Fri, Sep 17, 2004 at 04:15:23PM -0400, Stas Bekman wrote:
So is that the right skip rule (hoping that 2.0.52 will fix NetBSD:
my $should_skip =
($^0 eq /^OpenBSD$/i && !need_min_apache_version('2.0.51')) ||
($^0 eq /^NetBSD$/i && !need_min_apache_version('2.0.52'));
of co
On Fri, Sep 17, 2004 at 04:15:23PM -0400, Stas Bekman wrote:
> So is that the right skip rule (hoping that 2.0.52 will fix NetBSD:
>
> my $should_skip =
> ($^0 eq /^OpenBSD$/i && !need_min_apache_version('2.0.51')) ||
> ($^0 eq /^NetBSD$/i && !need_min_apache_version('2.0.52'));
That log
Ken Simpson wrote:
So is that the right skip rule (hoping that 2.0.52 will fix NetBSD:
my $should_skip =
($^0 eq /^OpenBSD$/i && !need_min_apache_version('2.0.51')) ||
($^0 eq /^NetBSD$/i && !need_min_apache_version('2.0.52'));
and the tests that need to be skipped are:
t/filter/both_str_con
On 17-Sep-04, at 4:55 PM, Stas Bekman wrote:
Geoffrey Young wrote:
Rici Lake wrote:
[...]
As a little bonus, it adds the
directive PerlUnsetVar
hmm... I guess this would be useful. but what does it do, unset the
last
value (of multiple adds) or clear the table entry entirely? if the
latter
may
Geoffrey Young wrote:
Rici Lake wrote:
[...]
As a little bonus, it adds the
directive PerlUnsetVar
hmm... I guess this would be useful. but what does it do, unset the last
value (of multiple adds) or clear the table entry entirely? if the latter
maybe PerlResetVar or PerlClearVar instead? also
Rici Lake wrote:
>
>
> Begin forwarded message:
>
>> From: Rici Lake <[EMAIL PROTECTED]>
>> Date: September 17, 2004 3:26:00 PM GMT-05:00
>> To: [EMAIL PROTECTED]
>> Subject: [mp2] patch for addvar/setvar merging
>>
>> Following is a patch which I believe fixes the mp2 outstanding issue
>> wit
Okay, but I want my (quasi-production) environment to
remain stable and I don't want to expose it to
constant patches. This will be even more important
once 2.0 becomes official. Maybe this doesn't really
apply to MP, but I also wouldn't want to break any
dependencies that other modules have (i.e.
Hi
MKDoc, a mod_perl, accessible, standards compliant, UTF-8, web
content management system has been GPL'ed:
http://mkdoc.com/news/gpl/
The stable version is available for download here:
http://download.mkdoc.com/mkdoc-1.6/mkdoc-1.6.28.tar.gz
There is also a news item about it pending at
--- Stas Bekman <[EMAIL PROTECTED]> wrote:
> Thomas Hilbig wrote:
>
> > I hope I'm not re-hashing an old issue, but I have
> > always found the MP bug tracking to be difficult.
> If
> > I see something peculiar (possible bug) there
> isn't a
> > bug database to search to see if it is new, or
>
Begin forwarded message:
From: Rici Lake <[EMAIL PROTECTED]>
Date: September 17, 2004 3:26:00 PM GMT-05:00
To: [EMAIL PROTECTED]
Subject: [mp2] patch for addvar/setvar merging
Following is a patch which I believe fixes the mp2 outstanding issue
with PerlAddVar/PerlSetVar ordering. As a little bon
Joe Orton wrote:
I can try and debug this, I've found a NetBSD machine and reproduced the
failure. ./t/TEST -start-httpd doesn't work from the mod_perl test
suite, is there a way to get that working?
I guess it will take a while to resolve these BSD issues. Meanwhile we
want to release 1.99_17 so
Arnaud Blancher wrote:
thank you
it's seems to be ok.
i ll read again closure in camel book !
See also:
http://perl.apache.org/docs/general/perl_reference/perl_reference.html#Understanding_Closuresthe_Easy_Way
--
__
Stas Bekman
Thomas Hilbig wrote:
I hope I'm not re-hashing an old issue, but I have
always found the MP bug tracking to be difficult. If
I see something peculiar (possible bug) there isn't a
bug database to search to see if it is new, or fixed
in later versions. Is there no repository for logging
MP bugs? W
I have to admit that I have been using MP2 in a
quasi-production environment. It has been very stable
(no crashes) but I have been very shy to apply any new
changes for some time (Apache 2.0.46, mod_perl
1.99_10, OpenSSL 0.9.7b) for fear it would de-stablize
the environment. I am very much lookin
thank you
it's seems to be ok.
i ll read again closure in camel book !
Arnaud
You are creating a closure. Easy to fix:
use My_module;
my $user = My_module->new(ip=>$ENV{'REMOTE_ADDR'},pid=>$$);
&taff2();
Make that:
taff2($user);
sub taff2 {
add this to the beginning of taff2:
my $user = shift;
-
Arnaud Blancher wrote:
i would like all my variable aren't share
and especially the $user object
You are creating a closure. Easy to fix:
use My_module;
my $user = My_module->new(ip=>$ENV{'REMOTE_ADDR'},pid=>$$);
&taff2();
Make that:
taff2($user);
sub taff2 {
add this to the beginning of taff2:
my
Enrico Sorcinelli wrote:
I'm glad to announce Apache::Session::Memcached.
This module provides a way to use memcached as Apache::Session storage
implementation
I wouldn't recommend using memcached for storing sessions. Memcached is
explicitly unreliable storage. It is built with the premise that
the complete config:
-8<-- Start Bug Report 8<--
1. Problem Description:
[DESCRIBE THE PROBLEM HERE]
2. Used Components and their Configuration:
*** mod_perl version 1.9914
*** using lib/Apache/BuildConfig.pm
*** Makefile.PL options:
MP_AP_PREFIX=> /usr
hi all
with mp2 1.99_14,perl 5.8.5,apache 2.0.50
i have a problem of persistance.
I just print IP, time and pid.
when 2 computer get the script they sometimes see the have the same IP
and the same time !
i would like all my variable aren't share
and especially the $user object
so could you tell
The uploaded file
Apache-Session-Memcached-0.02.tar.gz
has entered CPAN as
file: $CPAN/authors/id/E/EN/ENRYS/Apache-Session-Memcached-0.02.tar.gz
size: 4141 bytes
md5: 15481d872dc8dd2cf8e319903d139b17
---
I'm glad to announce Apache::Session::Memcached.
This module provides a way to
26 matches
Mail list logo
