Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 88276 invoked by uid 500); 12 Apr 2001 09:03:13 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 87740 invoked from network); 12 Apr 2001 09:02:55 -0000 Sender: harrie@lisanza.net Message-ID: <3AD49A57.B13FA0AB@covalent.net> Date: Wed, 11 Apr 2001 19:54:31 +0200 From: Harrie Hazewinkel Organization: Covalent Technologies X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: [PATCH] mpm_query References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N rbb@covalent.net wrote: > > On Wed, 11 Apr 2001, Harrie Hazewinkel wrote: > > > rbb@covalent.net wrote: > > [snip] > > > > > > Why is this useful? Isn't it more useful to know whether it is threaded > > > or process based. Between that information and the OS, is that enough? I > > > would rather add information like THREADS_DYNAMIC or THREADS_STATIC and > > > PROCESSES_DYNAMIC or PROCESSES_STATIC, to basically say if the number of > > > threads/process is static or not, and if the number of processes is > > > static. > > > > > > I want to decouple the MPM query function from an actual name. The goal > > > should be to report the properties of the MPM, not which exact MPM was > > > used. Once that is done, the need for the string disappears. > > > > That means, you cannot determine the MPM used. The values > > IS_THREADED and IS_FORKED are not uniquely identifying. > > The MPM type determines how the threads and processes are > > handled. For instance, perchild and threaded are both > > IS_THREADED == 1 and IS_FORKED == 1. > > That's true, but take a look at what I suggested please. I suggested > adding two more queries. THREADS_STATIC and PROCESSES_STATIC Yes, I noted that, but tomorrow some other MPM with similar features comes up. Providing the MPM via its name even if that could clash, but will most likely clash less. For instance, company foo would call there derived threaded MPM foo_threaded and company bar would call there derived threaded MPM bar_threaded. And they have similar features to threaded. > Now, we get the following results: > > threaded > IS_THREADED 1 > IS_FORKED 1 > THREADS_STATIC 1 > PROCESSES_STATIC 0 > > perchild > IS_THREADED 1 > IS_FORKED 1 > THREADS_STATIC 0 > PROCESSES_STATIC 1 > > My goal is to not rely on the name at all. We have already changed the > name of the threaded MPM once, and there have been peple talking about > changing the name of the OS/2 and Windows MPMs. We don't want to rely on > the names for anything outside of the MPM if we can avoid it at all. > > This function should be querying operational properties of the MPM, not > specific details of the MPM. > > Ryan > > _______________________________________________________________________________ > Ryan Bloom rbb@apache.org > 406 29th St. > San Francisco, CA 94131 > ------------------------------------------------------------------------------- -- phone: +39-3474932300 http://www.lisanza.net/