Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 10593 invoked by uid 500); 28 Mar 2000 01:00: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 10579 invoked from network); 28 Mar 2000 01:00:17 -0000 Date: Mon, 27 Mar 2000 17:05:04 -0800 (PST) From: Greg Stein To: new-httpd@apache.org Subject: Re: cvs commit: apache-2.0/htdocs/manual/developer layeredio.html index.html In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 27 Mar 2000, Dean Gaudet wrote: > On Sun, 26 Mar 2000, Greg Stein wrote: > > > Modules that are interested in inserting a layer should do so during the > > request processing. > > impossible -- mod_cgi doesn't know until it's in invoke_handler that its > response will need to have other filters stacked on top of it. Per my other message. Excellent point. Solvable, I believe, by re-running the "register processors" hook. > > Content-generating modules should continue to use > > ap_get_client_block() for reading, > > no change was made to this part of the API. Yes there was. Ryan introduced ap_setup_api(). That appears to be redundant to ap_setup_client_block(). > > and ap_r* for writing. Layers should be > > underneath those covers. > > impossible without asynchronous handlers. I'm not sure what you mean by "asynchronous handlers." The processors can block on a pipe, or use a callback and state machine. Is the state machine what you meant by async handler? Cheers, -g -- Greg Stein, http://www.lyra.org/