Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 19729 invoked by uid 500); 13 Dec 2001 21:45:11 -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: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 19718 invoked from network); 13 Dec 2001 21:45:10 -0000 Sender: gregames@Mail.MeepZor.Com Message-ID: <3C192156.D612101D@remulak.net> Date: Thu, 13 Dec 2001 16:44:54 -0500 From: Greg Ames X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19-10mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: Considering the Default Handler and Subrequests References: <056101c18343$024aab60$93c0b0d0@v505> <0b1701c18418$2791c270$93c0b0d0@v505> <0b3d01c1841a$33777f10$93c0b0d0@v505> <20011213212003.6A95F46E02@koj.rkbloom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ryan Bloom wrote: > > I still think the handler_fn function is overkill. The performance of Apache 1.3 > wasn't bad, because we did sane string compares, making sure that the > lengths were equal before doing a full strcmp. You're right, 1.3 was faster than the way we do it now. But we could do better still. I was thinking of something like a hash or a trie search for exact matches on r->handler. But then OtherBill got me thinking that if a module decided that it could serve the request in some earlier phase, it ought to be able to do something to latch on to the handler phase and eliminate most of the searching altogether. Greg