Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 90259 invoked by uid 500); 19 Jun 2001 19:56:49 -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 90176 invoked from network); 19 Jun 2001 19:56:37 -0000 X-Authentication-Warning: adsl-77-241-65.rdu.bellsouth.net: trawick set sender to trawick@attglobal.net using -f Sender: trawick@bellsouth.net To: new-httpd@apache.org Subject: Re: plz vote on tagging current CVS as APACHE_2_0_19 References: From: Jeff Trawick Date: 19 Jun 2001 15:48:19 -0400 In-Reply-To: Message-ID: Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N rbb@covalent.net writes: > -1. We already tagged 2.0.18, and rejected releasing it as a beta because > of the threaded MPM issues. I don't know who "we" is but I didn't like it because it didn't work nearly as as well as 2.0.16, regardless of the MPM :) > If we can wait about 1 week, I should have > the time to implement the design I posted back when we tagged > 2.0.19. Is that the new-and-improved pod+connect() design? If so, I have a patch on new-httpd (and private code that works a bit better). We still don't know how to portably kill threads non-gracefully though AFAIK. If it is not the new-and-improved pod+connect() design, what is it? (I've looked in new-httpd April-June; I don't doubt its there but a hint would be useful.) -- Jeff Trawick | trawick@attglobal.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...