Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 18574 invoked by uid 500); 30 Mar 2000 02:25:18 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 18560 invoked from network); 30 Mar 2000 02:25:17 -0000 Date: Wed, 29 Mar 2000 20:25:16 -0600 From: Manoj Kasichainula To: new-httpd@apache.org Subject: Re: Connection status docs. Message-ID: <20000329202516.F7727@io.com> Mail-Followup-To: new-httpd@apache.org References: <200003292255.RAA15049@devsys.jaguNET.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.9-current-20000328i In-Reply-To: ; from rbb@apache.org on Wed, Mar 29, 2000 at 06:14:43PM -0500 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Wed, Mar 29, 2000 at 06:14:43PM -0500, Ryan Bloom wrote: > > Well, until we get some docs, so that we all understand what it is > supposed to do, nobody can really even flesh it out. The major problems with the connection status stuff now are: - We need a better way to deal with multiple requests per connection. The functions are really simple right now because I didn't want to maintain complicated structures in shared memory, but this means that it's harder to eliminate status data on a connection that only pertains to old requests. Maybe it's time to implement the status table with message passing instead... - There just needs to be more use of the table. All you need to do is find a place where you want to add some per-connection status data, and call ap_update_connection_status(). Search for such a call in http_protocol.c for an example.