On Monday 23 April 2007 07:08, Philippe M. Chiasson wrote:
> > Is there something like $r->release_interp_after_this_phase()?
>
> Nope, but writing one would be very simple, all that's needed is
> to call
>
> MpInterpPUTBACK_On(interp)
>
apr_pool_cleanup_kill(r->pool, r, modperl_config_req_c
On 28-Feb-07, at 2:04 AM, Torsten Foertsch wrote:
Hi,
the default interpreter scope is request. That means a certain
interpreter is
locked during the whole request cycle.
That's correct.
I use modperl mostly in the
pre-response phases plus sometimes as an output filter. But
Torsten Foertsch wrote:
I use pnotes to
pass data between the phases. If I understand it correctly this forbids a
handler interpreter scope.
You might try using notes() instead, since I don't think it cares about
which interpreter is used. You can use Storable to stuff things into i
On Wed, 28 Feb 2007 11:04:14 +0100
Torsten Foertsch <[EMAIL PROTECTED]> wrote:
> Hi,
>
> the default interpreter scope is request. That means a certain
> interpreter is locked during the whole request cycle. I use modperl
> mostly in the pre-response phases plus sometime
Hi,
the default interpreter scope is request. That means a certain interpreter is
locked during the whole request cycle. I use modperl mostly in the
pre-response phases plus sometimes as an output filter. But I use pnotes to
pass data between the phases. If I understand it correctly this
