www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2025-08-05 16:55:50 +03:00
Code Activity

Fix typos.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@84841 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Tony Finch
2000-03-26 19:03:49 +00:00
parent d3de5e451d
commit c75543bdce
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/manual/developer/layeredio.html
View File

@@ -37,10 +37,10 @@ set the handler field to NULL, and allow the core to choose the which
module gets run next. If these two fields are not modified, then the server module gets run next. If these two fields are not modified, then the server
will loop forever calling the same module's handler. will loop forever calling the same module's handler.
<P>Most module's should not write out to the network if they want to take <P>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 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 request_rec, one for 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 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, 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. 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, This function checks to determine if the previous module set the input field,
@@ -55,10 +55,10 @@ the same pipe.
<H3>An Example of Layered I/O.</H3> <H3>An Example of Layered I/O.</H3>
<P>This example is the most basic layered I/O example possible. It is <P>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.
<P>mod_cgi executes the cgi script, and then sets request_rec->input to <P>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, sets request_rec->content_type to whatever the CGI writes out (in this case,
text/html). Finally, mod_cgi returns RERUN_HANDLERS. text/html). Finally, mod_cgi returns RERUN_HANDLERS.