Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Date: Sat, 6 Nov 2004 09:30:31 -0500 (EST)
From: Cliff Woolley <jwoolley@virginia.edu>
To: dev@httpd.apache.org
Subject: Re: Use threaded MPM by default was Re: cvs commit: httpd-2.0 STATUS
In-Reply-To: <418CD9A6.6000907@modperlcookbook.org>
Message-ID: <Pine.GSO.4.58.0411060929120.26816@cobra.cs.Virginia.EDU>
References: <20041106082824.55145.qmail@minotaur.apache.org>
 <99D0677E0FB470CB870D5EAB@[10.0.1.80]> <418CD9A6.6000907@modperlcookbook.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 6 Nov 2004, Geoffrey Young wrote:

> MPM on a platform that does not support it, the build process silently
> switches to prefork (or whatever the default is for the platform, I guess)
> now, I haven't seen this myself, so I don't want to propagate FUD, but if
> it's true I might suggest that halting the build process is preferable to
> switching behind the scenes (or even switching with a little warning) - from

That does seem to match my memory of the situation, fwiw.  I would have no
problem with halting the build if they specified --with-threads and none
were available, though I would have a problem with halting the build if
using a threaded MPM were simply used by default and none were available.

--Cliff