Philippe M. Chiasson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stas Bekman wrote:
| I've further simplified the handler. the following
| [...]
Sorry for the slight lag in looking into this one, but I will have a look
shortly. I have the feeling that this is caused by how we 'cache'
hand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stas Bekman wrote:
| I've further simplified the handler. the following
| [...]
Sorry for the slight lag in looking into this one, but I will have a look
shortly. I have the feeling that this is caused by how we 'cache' handler subs
references instead o
Geoffrey Young wrote:
Stas Bekman wrote:
Let's stop that drag. Clearly it's only me who's against this change. So
please take out your sharp knives and make a clear cut.
if you want to do it that quickly we can, but voting now seems a bit
premature. has anyone other than joe, randy, and I actuall
Stas Bekman wrote:
Stas Bekman wrote:
[...]
First of all we have to separate the objects in two groups: those
created by users (1) and those created by Apache/mp2 (2).
(1) things which are completely under user control look easy, for
example if you create an APR::Table object, we can clone it by
Stas Bekman wrote:
> Let's stop that drag. Clearly it's only me who's against this change. So
> please take out your sharp knives and make a clear cut.
if you want to do it that quickly we can, but voting now seems a bit
premature. has anyone other than joe, randy, and I actually tried the
code
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Joe Schaefer wrote:
[...]
Then let's flesh out the consequences, and assume it will be
fixed in 2.2. What I'm having difficulty understanding
here is this: how does renaming Apache::FilterRec to
Apache2::FilterRec now make any differe
Stas Bekman <[EMAIL PROTECTED]> writes:
> Why not? How can you decide for a user that it's OK for them
> to have mp1 and mp2.0 at the same time, but not mp2.0 and mp2
It's not a question of ok or not ok; it's a question of interface
compatibility. You simply cannot have two incompatible
Apache:
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Joe Schaefer wrote:
[...]
Then let's flesh out the consequences, and assume it will be
fixed in 2.2. What I'm having difficulty understanding
here is this: how does renaming Apache::FilterRec to
Apache2::FilterRec now make any differe
Stas Bekman <[EMAIL PROTECTED]> writes:
> Joe Schaefer wrote:
[...]
>> Then let's flesh out the consequences, and assume it will be
>> fixed in 2.2. What I'm having difficulty understanding
>> here is this: how does renaming Apache::FilterRec to
>> Apache2::FilterRec now make any difference wh
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Everything and anything is possible. I believe that bug in filter
stack is a showstopper for Apache 2.2 release. And Justin has said
precisely that it'll be fixed in 2.2, when I've reported it some 2
years ago.
Then let's flesh out the
Stas Bekman <[EMAIL PROTECTED]> writes:
> Everything and anything is possible. I believe that bug in filter
> stack is a showstopper for Apache 2.2 release. And Justin has said
> precisely that it'll be fixed in 2.2, when I've reported it some 2
> years ago.
Then let's flesh out the consequences
Stas Bekman wrote:
Let's stop that drag. Clearly it's only me who's against this change. So
please take out your sharp knives and make a clear cut.
This a vote is to decide whether mod_perl2 should have its API renamed
as follows: s/Apache::/Apache2::/g.
-1
--
___
Let's stop that drag. Clearly it's only me who's against this change. So
please take out your sharp knives and make a clear cut.
This a vote is to decide whether mod_perl2 should have its API renamed as
follows: s/Apache::/Apache2::/g.
This vote is open only to committers. According to ASF laws
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Here is an example I've mentioned before. mp2.2 major release may be
required really soon if the filters stack will be changed in Apache
2.2, since it'll make some of the filtering API different in an
incompatible way with 2.0.
I think i
Stas Bekman <[EMAIL PROTECTED]> writes:
> Here is an example I've mentioned before. mp2.2 major release may be
> required really soon if the filters stack will be changed in Apache
> 2.2, since it'll make some of the filtering API different in an
> incompatible way with 2.0.
I think it's also jus
15 matches
Mail list logo
