> Generally, about the time you get to caching, you also want a split > server. I'm successfully using a thin-caching-front, > thick-mod_perl-back split server, where both docroots point at the > same tree. The advantage is that I can quickly decide that something > can be served entirely from the front. I can also implement various > caching policies in the back with mod_expires. It's quite sweet.
So basically I would need to use two apaches... Currently, the way we're set up is that we've got one apache which runs multiple sites on the same mod_perl code using VirtualHost. How would that work with two apaches? Would I need the front-end apache running on port 80 and the back end on some other port? If that were the case, would the front end, translate addresses such as http://mkdoc.com/ to http://mkdoc.com/:8080 ? That would be a problem since the http://mkdoc.com/:8080 would have hyperlinks such as http://mkdoc.com/features/:8080, which would effectively make the cache useless. Another problem with this approach is that we already run a second apache for https on some sites... That would give a total of three or four separate apaches to maintain. We've got 3 boxes that run different sites. That'd make our system administrator go nuts (and I would understand...), which is why I'd like to keep the caching code within the software so that we simply need to do a CVS up and maybe change Apache::Registry to Apache::CachedRegistry or something... Cheers, -- Building a better web - http://www.mkdoc.com/ --------------------------------------------- Jean-Michel Hiver [EMAIL PROTECTED] - +44 (0)114 255 8097 Homepage: http://www.webmatrix.net/ -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
