Is it within the scope of mod_perl2 to duplicate its interpreter pool framework?
Intention: To have separate interpreter pools for directories /test1 and /test2 So that: - $MyModule::request_count++ would track access to each directory - chdir() in a script under /test1 would not affect cwd() on /test2 - $main::mySingleton is maintained twice - etc It is my current desire to go away from FastCGI and embrace mod_perl. For those familiar with FastCGI, I am wanting mod_perl2 to work the same way. I am flooded with numerous options as I read through the mod_perl2 documents, and it seems that what I want from mod_perl is far from the design goal: "Provide complete access to the Apache C API via the Perl programming language." Yet necessary to acheive the acclaimed: "Accelerate your existing dynamic content ... A few changes to the web server's config is all that is required to run your existing CGI scripts at lightning speed." So, am I missing the ball and should go read ____? This is a worthy effort to the mod_perl2 community and I should join the team? This isn't within the design goals for mod_perl2, but a PerlRequestHanlder could be written? Thank you for any time you spend on this. As this is my first post, please educate me if I need it ;) -Ryan -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
