Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 83862 invoked by uid 500); 12 Oct 2002 03:28:05 -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 83849 invoked from network); 12 Oct 2002 03:28:04 -0000 Message-ID: <3DA796CE.2060105@cnet.com> Date: Fri, 11 Oct 2002 20:28:14 -0700 From: Brian Pane User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@httpd.apache.org Subject: Re: apache 2.0.43: %b not showing "bytes sent" but "bytes requested" References: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N rbb@apache.org wrote: >What we are learning here is simple. We need to do the counting in the >core_output_filter. If that means adding a field to the conn_rec, or >somehow getting the request_rec in the core_output_filter doesn't >matter. The count needs to be done in the core_output_filter, by tallying >the amount of data actually written. > > Yes, exactly. The only problem is that this will require a design change. Currently, the last write can complete after the request_rec no longer exists (if the connection is a keepalive). Solving this is tricky. One possibility is to transfer ownership of the the request (including its pool) to the core output filter as soon as we pass an EOF to that filter. That would complicate the memory management a bit, but it might be worth the effort because it would give us almost all the infrastructure needed to support a semi-async MPM. Brian