Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <3A8AAEB6.EABDF847@Golux.Com>
Date: Wed, 14 Feb 2001 11:13:42 -0500
From: Rodent of Unusual Size <Ken.Coar@Golux.Com>
Organization: The Apache Software Foundation
MIME-Version: 1.0
To: new-httpd@apache.org
Subject: Re: Server directives
References: <000d01c0960c$c428dc40$7201a8c0@SASHIMI>
 <3A89B77B.197593B@Golux.Com> <009201c0961e$4847e370$7201a8c0@SASHIMI>
 <03ef01c0961e$508cbd80$95c0b0d0@roweclan.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"William A. Rowe, Jr." wrote:
> 
> "Servers" doesn't cut it.  If you switch MPM's, you have to
> switch your directives.  You can't just s/processes/threads/
> and expect the server will have the same profile/memory
> consumption/cpu utilization etc.

No, but neither should you have to munge your config files
each time you change MPMs until you find the right fit.  *That*
is bogus.

Come up with a name for an entity capable of handling a request,
and use that name across MPMs and let them translate it into
the appropriate significance.  Yes, MPMs can have different
directives for non-portable concepts (as 'threads' means
something to pthreads and perchild, but not prefork), but use
a common name for project-wide common concepts.
-- 
#ken    P-)}

Ken Coar                    <http://Golux.Com/coar/>
Apache Software Foundation  <http://www.apache.org/>
"Apache Server for Dummies" <http://Apache-Server.Com/>
"Apache Server Unleashed"   <http://ApacheUnleashed.Com/>