On Wed 21 Oct 2009, Alan Young wrote: > http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_
Unfortunately the Parent option works only in vhosts. But I believe it could be hacked to work also for directory containers. Of course PerlPostReadRequest, PerlTranslation and PerlMapToStorage phases are handled by the main interpreter for the vhost. But just before the PerlHeaderParserHandler is called one could check if the rest of the request cycle is to be handled by a different interpreter and fetch one from a cache or instantiate a new one. Of course the user would have to know what he is doing using this feature. For example setting a PerlResponseHandler where the handler routine is an anonymous sub in the translation phase would not work as expected. An alternative would be to have modperl inspect the uri prior to PerlPostReadRequest and decide what interpreter to use based on it, similar to what ServerPath does. Then the same interpreter would handle all phases. Torsten -- Need professional mod_perl support? Just hire me: torsten.foert...@gmx.net
