On Tue, Oct 13, 2009 at 8:08 AM, Scott Gifford <sgiff...@suspectclass.com> wrote: >> Sounds like you might be pushing the envelope on what Apache can >> actually do. If you cannot solve the problem in Apache you could >> consider relying on Apache default vhost as a way to funnel all >> requests into a Perl "dynamic vhost" implementation. You get exactly >> what your looking for, but you tradeoff the speed and maturity of >> Apache vhost code for yours. > > Thanks, I will definitely take a look! Do you have any recommended > reading on this, or just what Google turns up for "dynamic vhost"?
I don't know of anything that specifically does this, then again I havn't looked. I was mainly thinking about pushing the problem into a different layer since I wasn't sure the Apache layer would work. If it were me I would probably start by looking for through "Mass Dynamic Virtual Hosting" and make sure you can't solve your problem in the Apache layer, or with a ModPerl Apache module to extend Apache (either one already written, or one you write yourself). Then move on to Perl code that does webserving. -wjt
