Return-Path: Delivered-To: apmail-apache-cvs-archive@apache.org Received: (qmail 66604 invoked by uid 500); 26 Mar 2000 19:03:50 -0000 Mailing-List: contact apache-cvs-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 apache-cvs@apache.org Received: (qmail 66591 invoked by uid 500); 26 Mar 2000 19:03:49 -0000 Delivered-To: apmail-apache-2.0-cvs@apache.org Date: 26 Mar 2000 19:03:49 -0000 Message-ID: <20000326190349.66587.qmail@locus.apache.org> From: fanf@locus.apache.org To: apache-2.0-cvs@apache.org Subject: cvs commit: apache-2.0/htdocs/manual/developer layeredio.html fanf 00/03/26 11:03:49 Modified: htdocs/manual/developer layeredio.html Log: Fix typos. Revision Changes Path 1.3 +5 -5 apache-2.0/htdocs/manual/developer/layeredio.html Index: layeredio.html =================================================================== RCS file: /home/cvs/apache-2.0/htdocs/manual/developer/layeredio.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- layeredio.html 2000/03/26 09:39:36 1.2 +++ layeredio.html 2000/03/26 19:03:49 1.3 @@ -37,10 +37,10 @@ module gets run next. If these two fields are not modified, then the server will loop forever calling the same module's handler. -

Most module's should not write out to the network if they want to take +

Most modules should not write out to the network if they want to take advantage of layered I/O. Two BUFF structures have been added to the -request_rec, one of input, and one for output. The module should read and -write to these BUFF's. The module will also have to setup the input field for +request_rec, one for input and one for output. The module should read and +write to these BUFFs. The module will also have to setup the input field for the next module in the list. A new function has been added, ap_setup_input, which all modules should call before they do any reading to get data to modify. This function checks to determine if the previous module set the input field, @@ -55,10 +55,10 @@

An Example of Layered I/O.

This example is the most basic layered I/O example possible. It is -basically CGI's generated by mod_cgi and sent to the network via http_core. +basically CGIs generated by mod_cgi and sent to the network via http_core.

mod_cgi executes the cgi script, and then sets request_rec->input to -the output pipe of the CGI. It then NULL's out request_rec->handler, and +the output pipe of the CGI. It then NULLs out request_rec->handler, and sets request_rec->content_type to whatever the CGI writes out (in this case, text/html). Finally, mod_cgi returns RERUN_HANDLERS.