Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 21885 invoked from network); 12 Nov 2009 14:07:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Nov 2009 14:07:14 -0000 Received: (qmail 15527 invoked by uid 500); 12 Nov 2009 14:07:13 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 15416 invoked by uid 500); 12 Nov 2009 14:07:13 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 15407 invoked by uid 99); 12 Nov 2009 14:07:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 14:07:13 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 76.96.59.227 is neither permitted nor denied by domain of jim@jagunet.com) Received: from [76.96.59.227] (HELO QMTA12.westchester.pa.mail.comcast.net) (76.96.59.227) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Nov 2009 14:07:03 +0000 Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA12.westchester.pa.mail.comcast.net with comcast id 4ByW1d0011HzFnQ5CE6jja; Thu, 12 Nov 2009 14:06:43 +0000 Received: from [192.168.199.10] ([69.251.84.64]) by OMTA14.westchester.pa.mail.comcast.net with comcast id 4E6i1d00a1PGofZ3aE6jRC; Thu, 12 Nov 2009 14:06:43 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) Subject: Re: Httpd 3.0 or something else From: Jim Jagielski In-Reply-To: Date: Thu, 12 Nov 2009 09:06:42 -0500 Content-Transfer-Encoding: 7bit Message-Id: References: To: dev@httpd.apache.org X-Mailer: Apple Mail (2.1077) X-Virus-Checked: Checked by ClamAV on apache.org On Nov 11, 2009, at 2:14 PM, Akins, Brian wrote: > On 11/10/09 6:20 PM, "Greg Stein" wrote: > >> I'd like to see a few "network" threads multiplexing all the writing >> to clients. > > That's what I meant. I just didn't state it properly. > > >> Then take all of *that*, and spread it across several processes for >> solid uptime, with a master monitor process. > > And then you have nginx ;) > Well, nginx is, after all, a fork of httpd....