On Wed, 2003-05-14 at 14:14, Simon Wilcox wrote:
> Yep. The problem is that A::T doesn't work across virtual hosts. No-one
> seems to have had the skillz and/or tuits to fix it.
mod_perl might just be the wrong thing for the job.
How about thttpd and speedycgi instead? Then you could start a new set
of speedycgi processes for each virtual host.
It seems unlikely, but in practice it seems to work very well. For
example for the glastonbury festival website, the apache/mod_perl/tt
combination couldn't keep up with peak traffic. So we switched to our
backup plan thttpd serving cached content, and never turned back.
Now, the parts that need to be dynamic ( for example
http://www.glastonburyfestivals.co.uk/dyn/dvd/ ) go via speedycgi.
'dyn' is actually a speedycgi script. That speedycgi just translates
the url path to a template path, in a similar way to how I imagine
Apache::Template does.
But if you want a whole virtual host to be dynamic, you can do that by
switching vhosting on for thttpd, and making what is normally the
subdirectory for the virtualhost a speedycgi script.
Damn fast, and without all the hassles of apache.
http://www.acme.com/software/thttpd/
- seems to be some inconsistency with the paths that thttpd passes to
CGI though
http://daemoninc.com/SpeedyCGI/
- you'd want to set a different 'group' for each virtual host, and tweek
the 'maxbackends', 'maxruns' and similar parameters.
alex
--
alex <alex-zpEUbJRnd28qdlJmJB21zg@xxxxxxxxxxxxxxxx>
|
