perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank Wiles <fr...@wiles.org>
Subject Re: Interpreter scope
Date Wed, 28 Feb 2007 15:10:39 GMT
On Wed, 28 Feb 2007 11:04:14 +0100
Torsten Foertsch <torsten.foertsch@gmx.net> 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 sometimes as an output filter.
> But I use pnotes to pass data between the phases. If I understand it
> correctly this forbids a handler interpreter scope. Now I'd like to
> release the interpreter in most cases just before the response phase.
> So it can be reused by another request while the current request
> sends its data over a possibly slow network.
> 
> Is that reasonable?
> 
> Is there something like $r->release_interp_after_this_phase()?
> 
> If not what is the right place to start looking/patching? And what
> pitfalls are there to watch out?

   Have you looked into using a lightweight front end setup to handle
   this?  I've had great success with the more traditional light/heavy
   Apache setup with mod_proxy, perlbal is awesome, and know 
   many people who use things like lighttpd or pound. 

 ---------------------------------
   Frank Wiles <frank@wiles.org>
   http://www.wiles.org
 ---------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message