Assuming you can load 5000 virtual servers into memory, and protect them, etc. The startup time would be huge. Also, each virtual server would need their own database handles, which would be open all the time. I once tested starting up 500 virtual servers under AOLserver 2.3.3. I didn't have enough memory, but, for basic, no frills AOLserver instances, 200 or so took minutes to startup.
Also, you should seriously consider the problem of allowing even one user having scripting control of a stand alone AOLserver in your hosting environment. It is probably safer than a shell, but by how much? Poor programming choices can quickly clog up an entire server. If you consider code review as an option, you can pursue a virtual hosting solution which would combine all the servers into one server, and just set the pageroot accordingly. There are numerous options for doing this. The newest is the use of the ns_rewrite module. I wrote the doc on that and included an example of virtual hosting: http://zmbh.com/nsrewrite/ Or check at http://aolserver.com/ tom jackson -- 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.
