Hi All, I'm developing a multi-httpd configuration with the http accelerating proxy, well practically the same that was described in the Apache mod_perl guide. 2 httpd+mod_perl - one for very fast process with low need in modules, and the other one for statistics, near 1MB of modules, much slower in comparence with the 1st one. And the 3rd - httpd+mod_proxy (or may be mod_accel by Igor Sysoev that I've read about only yesterday :)
Right now this all happens on one and the same machine with one ip-address. So, I've got the idea to attach busy mod_perl httpds to some unusual ports on 127.0.0.1 and make them available from localhost only. While proxy is supposed to handle 7+ name based virtual hosts (the number is DB-dependent) OK, this goes OK so far (cross fingers). Before this poin it worked very nice on one httpd with the large <Perl> section that includes DB call to find out which virtual hosts to initiate. But now with this httpd+mod_proxy I can't use <Perl> section because it shouldn't use mod_perl, right? It's supposed to be lightweight. Well, the question is, what if I'll load mod_perl only for <Perl> section parsing and generating the dynamic config with Apache->httpd_conf method, and no real mod_perl locations - would this still make server childs much bigger then without mod_perl? Sorry, as I'm mainly on Win32 and the production server is now built statically, I'm a little limited in experiments loading modules. I'd like to know also would the child-servers size depend on static/DSO installation of the proxy-httpd with mod_perl (again - to run on server statup only and parse <Perl> sections only). May be DSO httpd will load mod_perl.so on startup and not copy it to child servers as they don't need it? Or may be there is some way to un-load mod_perl after <Perl> sections processing? Thanks, any input is much appreciated -- ================================== Mike Blazer [EMAIL PROTECTED] ==================================
