Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 90472 invoked by uid 500); 13 Oct 2000 15:06:40 -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 90249 invoked from network); 13 Oct 2000 15:05:57 -0000 To: new-httpd@apache.org Subject: Re: cvs commit: apache-2.0/src/modules/standard mod_include.c References: <20001013053558.24976.qmail@locus.apache.org> From: Jeff Trawick Date: 13 Oct 2000 11:02:58 -0400 In-Reply-To: rbb@locus.apache.org's message of "13 Oct 2000 05:35:58 -0000" Message-ID: Lines: 28 X-Mailer: Gnus v5.5/Emacs 20.3 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N rbb@locus.apache.org writes: > rbb 00/10/12 22:35:58 > > Modified: src CHANGES > src/ap ap_buckets.c ap_buckets_eos.c ap_buckets_file.c > ap_buckets_heap.c ap_buckets_mmap.c > ap_buckets_pipe.c ap_buckets_simple.c > ap_buckets_socket.c > src/include ap_buckets.h > src/main http_core.c http_protocol.c util_filter.c > src/modules/experimental mod_charset_lite.c > src/modules/standard mod_include.c > Log: > Remove all function pointers from the ap_bucket type. These function > pointers are replaced with a global table that allows modules to register > their bucket types. Those bucket types are then allowed to be used in > the server processing. This also required removing all direct calls to > those functions. The ap_bucket type has an index into an array, so in > each ap_bucket_* function, we use that index to find the correct set of > functions. So how do I see if the bucket in hand is an EOS bucket without making a function call? !@#$%^&*!~!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -- Jeff Trawick | trawick@ibm.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...