Thorpe, First question is how many virtual hosts? Second is how busy?
The simple virtual server was an example of a no-configuration virtual server. It relies entirely on correctly setup DNS. I have written several other virtual servers (tclvhr and vat) which have slightly different features, but the common feature is that they use one AOLserver server instance, and thus economize memory use. If you have tens, hundreds or thousands of mostly idle websites, this is the way to go. But if you have a few sites that need to remain separated in memory/code, you should use AOLserver virtual servers. Also, speed will be better with AOLserver virtual servers, since it is done in C. For moderate load, there probably isn't any issue. If you need to serve hundreds of independent websites, use Apache 1.x, or buy lots of ram or additional machines. The one big issue with AOLserver handling many virtual servers is that each must load code separately, startup time increases as you add more hosts and eventually it will piss you off. tom jackson On Wednesday 28 February 2007 07:47, Thorpe Mayes wrote: > > This simply handled the question regarding the www. in the > rewriteRequest proc and eliminated the filter that would have called > the rewriteWWW proc. > > Do you see any issues with this approach? Any issues with using this as > a means to run virtual hosts on a moderately busy server? -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
