Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Date: Tue, 25 Jul 2000 17:25:15 +0000
From: Tony Finch <dot@dotat.at>
To: new-httpd@apache.org
Subject: Re: Anywhere to go for a summmary of I/O filtering?
Message-ID: <20000725172515.A444@hand.dotat.at>
References: <Pine.LNX.4.21.0007241034470.21368-100000@koj.rkbloom.net>
 <000101bff59b$439aaed0$345985d0@corecomm.net>
 <20000725021834.B1377@manojk.users.mindspring.com>
 <20000725032556.Y10898@lyra.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20000725032556.Y10898@lyra.org>
Organization: Covalent Technologies, Inc

Greg Stein <gstein@lyra.org> wrote:
>
>IMO, we should try to move away from the Directory section. It is filesystem
>specific and (slightly) hinders the move to repository independence.

+1

>That said: using a vhost as the granularity means that any requests arriving
>at a vhost have a single user/group. If you make it per-Loc, then you're
>going to need to start passing request handling between processes/threads.
>Possible? Dunno. But certainly more difficult, I'd think.

You have to pass requests from one thread to another for vhosts as
well, unless you restrict yourself to IP-based vhosting.

Tony.
-- 
f.a.n.finch    fanf@covalent.net    dot@dotat.at
285 sucker punch in the gut bucket