Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 41185 invoked by uid 500); 24 Jul 2001 16:08:31 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 41171 invoked from network); 24 Jul 2001 16:08:30 -0000 Date: Tue, 24 Jul 2001 09:08:06 -0700 From: Justin Erenkrantz To: new-httpd@apache.org, rbb@covalent.net Cc: dev@apr.apache.org Subject: Re: [PATH] MPMT single acceptor patch Message-ID: <20010724090806.L26972@ebuilt.com> References: <01072408445202.03564@koj.rkbloom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01072408445202.03564@koj.rkbloom.net>; from rbb@covalent.net on Tue, Jul 24, 2001 at 08:44:52AM -0700 X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N [ Adding dev@apr ] On Tue, Jul 24, 2001 at 08:44:52AM -0700, Ryan Bloom wrote: > > > This patch uses the original fdqueue.[ch] logic to implement the single acceptor, multiple > worker logic in the threaded MPM. The original fdqueue logic can be found in apache-apr, but > I have attached a copy to this message. Should we APRize the fdqueue.[ch] code and stick it in apr-util? It may be a little lightweight to merit that though. However, it also relies on pthread condition variables. Maybe now would be a good time to add condition variables to APR? Do other platforms have the concept of condition variables? (I know Aaron would love to see condition variables in APR.) -- justin