> >Netscape's Communications server requires that you reinstall the
> >product every time you want to add a new domain. Also, it spawns a
> >whole new set of processes to handle this domain.
> You don't have to reinstall the entire product each time -- you
> simply need a separate set of configuration files for each
> instance. The binaries are shared, and all of the servers are
> managed from a single, web-based administration utility.
> >What if you need to have 10, or 20, or more virtual domains? Won't
> >this eat up all you machines memory? Isn't NCSA 1.5 or Apache more
> Not by a long shot. The reason that several processes are run for
> each server is precisely *for* efficiency. The server doesn't have
> to go through all of the work of starting a new process to serve
> each request -- it can simply be served by a process that is ready
> and waiting.
> Also, the number of processes that remain in memory is completely
> configurable by you. You can set the minimum number of processes
> that will always remain in memory, and you can set the maximum
> number of additional processes that can be opened at periods of high
instance of the server to serve each domain, which can be a bit of a
pain. Suppose you have 20 domains on one solaris box, and each of
your customers wants to have peak performance, so demands that you
prefork 15 child processes for their domain. That's 300 processes
I'm not sure how apache or NCSA does the multi-domain stuff, so they
may or may not be more efficient.