From owner-freebsd-isp  Sun Jul 28 08:52:31 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA27742
          for isp-outgoing; Sun, 28 Jul 1996 08:52:31 -0700 (PDT)
Received: from ns2.win.net (ns2.win.net [204.215.209.4])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA27735
          for <freebsd-isp@freebsd.org>; Sun, 28 Jul 1996 08:52:27 -0700 (PDT)
Received: from launchpad.win.net (launchpad@localhost) by ns2.win.net (8.6.12/8.6.9) with UUCP id LAA22755 for freebsd-isp@freebsd.org; Sun, 28 Jul 1996 11:50:51 -0400
Received: by win.net!launchpad;  Sun, 28 Jul 1996 11:48:28
X-Mailer: WinNET Mail, v4.0a
Message-ID: <AC18@launchpad.win.net>
Reply-To: fbsd-isp@launchpad.win.net (Joe Mays - freebsd-isp)
To: freebsd-isp@freebsd.org
Date: Sun, 28 Jul 1996 11:48:27 -0400
Subject: Apache Virtual Website options
From: fbsd-isp@launchpad.win.net (Joe Mays - freebsd-isp)
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Up until now we have been using the cern server as our primary web
server.  We also have a few hundred virtual websites that have
been using the cern httpd_multi quite happily.  I just switched the
main server over to apache httpd with no problem, and we are
looking at switching all the virtual websites over to apache also.

Here's the question -- apache offers two options for running
virtual web sites.  You can use use the Bind option, which binds
the server to the ip number and runs a separate server daemon for
each virtual website (this more or less equates to what we are
doing now with cern), or you can use the Listen option to run
allow the primary daemon to also listen and respond to all the
virtual websites.

Does anyone have any input on which method offers more performance
when you get into the 200-300 virtual website realm?

Joe Mays