httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From f...@locus.apache.org
Subject cvs commit: apache-2.0/htdocs/manual/developer layeredio.html
Date Sun, 26 Mar 2000 19:03:49 GMT
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.
   
  -<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
  -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 @@
   <H3>An Example of Layered I/O.</H3> 
   
   <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 
  -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.
   
  
  
  

Mime
View raw message