Graham Dumpleton wrote:
On 19/02/2006, at 3:24 PM, Graham Dumpleton wrote:
Thus depending on what you are doing, you need one or the other. To
make it
obvious, should perhaps use a distinct method name to add handlers as
stacked
handlers against the current handler list. Thus:
def all(r
I'll post more later when I have a chance to check a few things, but
I am
going to backtrack a bit. How far I don't know yet.
In short for now, mod_perl has a a concept called stacked handlers. You
have stacked handlers when you list more than one handler with the
handler directive on the same
I agree with Deron's summary of your summary. :)
If we make this change (and that is a +1 from me) I suggest the
following path, assuming that it is possible to control this behaviour
with a PythonOption flag:
1. mp 3.3 - New behaviour is off by default, but can be turned on using
a PythonOp
Thanks for the feedback. At least I am not wacko. Further comments
below.
On 18/02/2006, at 5:44 PM, Deron Meranda wrote:
I guess the positive thing is that because of this I don't have
any existing code which actually uses multiple mod_python
handlers in the same phase; so this change in behav
On 2/17/06, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
> When you get a chance, can you read through the JIRA issue:
>
>http://issues.apache.org/jira/browse/MODPYTHON-129
>
> and provide some feedback on whether you think my analysis is correct
> and thus whether mod_python really needs to be
