diff options
| -rw-r--r-- | docs/manual/developer/layeredio.html | 4 | ||||
| -rw-r--r-- | docs/manual/new_features_2_0.html | 4 | ||||
| -rw-r--r-- | docs/manual/new_features_2_0.html.en | 4 |
3 files changed, 6 insertions, 6 deletions
diff --git a/docs/manual/developer/layeredio.html b/docs/manual/developer/layeredio.html index d090e9dc02..2369bc47b7 100644 --- a/docs/manual/developer/layeredio.html +++ b/docs/manual/developer/layeredio.html @@ -31,7 +31,7 @@ needed. A new return value has been added for modules, RERUN_HANDLERS. When a handler returns this value, the core searches through the list of handlers looking for another module that wants to try the request. -<P>When a module returns RERUN_HANDLERS, it must modify teo fields of the +<P>When a module returns RERUN_HANDLERS, it must modify two fields of the request_rec, the handler and content_type fields. Most modules will 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 @@ -44,7 +44,7 @@ write to these BUFF's. 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, -if so, that input is used, if not the file is opend and that data source +if so, that input is used, if not the file is opened and that data source is used. The output field is used basically the same way. The module must set this field before they call ap_r* in order to take advantage of layered I/O. If this field is not set, ap_r* will write directly to the diff --git a/docs/manual/new_features_2_0.html b/docs/manual/new_features_2_0.html index af41cc1185..d0ae3450eb 100644 --- a/docs/manual/new_features_2_0.html +++ b/docs/manual/new_features_2_0.html @@ -33,10 +33,10 @@ <DT><STRONG>Better support for non-Unix platforms</STRONG> <DD>Apache 2.0 should be faster and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific - multiprocessing modules and the Apache Portable Runtime, these + multiprocessing modules (MPM) and the Apache Portable Runtime, these platforms can now avoid using POSIX-emulation functions that are sometimes buggy and always hurt performance. - +<DD>A list of the MPM's currently available is <a href="mpm.html">here</a>. <DT><STRONG>New API</STRONG> <DD>The API for modules has changed significantly for 2.0. Many of the module-ordering problems from 1.3 should be gone. 2.0 does much of diff --git a/docs/manual/new_features_2_0.html.en b/docs/manual/new_features_2_0.html.en index af41cc1185..d0ae3450eb 100644 --- a/docs/manual/new_features_2_0.html.en +++ b/docs/manual/new_features_2_0.html.en @@ -33,10 +33,10 @@ <DT><STRONG>Better support for non-Unix platforms</STRONG> <DD>Apache 2.0 should be faster and more stable on non-Unix platforms such as BeOS, OS/2, and Windows. With the introduction of platform-specific - multiprocessing modules and the Apache Portable Runtime, these + multiprocessing modules (MPM) and the Apache Portable Runtime, these platforms can now avoid using POSIX-emulation functions that are sometimes buggy and always hurt performance. - +<DD>A list of the MPM's currently available is <a href="mpm.html">here</a>. <DT><STRONG>New API</STRONG> <DD>The API for modules has changed significantly for 2.0. Many of the module-ordering problems from 1.3 should be gone. 2.0 does much of |