diff options
| author | André Malo <nd@apache.org> | 2003-04-05 19:22:15 +0200 |
|---|---|---|
| committer | André Malo <nd@apache.org> | 2003-04-05 19:22:15 +0200 |
| commit | 68a2004c778afcd36ddf980e417a50783b91019f (patch) | |
| tree | 79dae0567e60f57f04950646583399a36b2e4ac0 | |
| parent | new XML (diff) | |
| download | apache2-68a2004c778afcd36ddf980e417a50783b91019f.tar.xz apache2-68a2004c778afcd36ddf980e417a50783b91019f.zip | |
the layeredio concept was never really applied. So drop this outdated document.
It may be confusing for people new to apache development.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@99241 13f79535-47bb-0310-9956-ffa450edef68
| -rw-r--r-- | docs/manual/developer/layeredio.html | 85 | ||||
| -rw-r--r-- | docs/manual/sitemap.html.de | 1 | ||||
| -rw-r--r-- | docs/manual/sitemap.html.en | 1 | ||||
| -rw-r--r-- | docs/manual/sitemap.xml | 1 | ||||
| -rw-r--r-- | docs/manual/sitemap.xml.de | 1 |
5 files changed, 0 insertions, 89 deletions
diff --git a/docs/manual/developer/layeredio.html b/docs/manual/developer/layeredio.html deleted file mode 100644 index a4d1f5cda4..0000000000 --- a/docs/manual/developer/layeredio.html +++ /dev/null @@ -1,85 +0,0 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - -<html xmlns="http://www.w3.org/1999/xhtml"> - <head> - <meta name="generator" content="HTML Tidy, see www.w3.org" /> - - <title>Apache 2.0 Layered I/O</title> - </head> - <!-- Background white, links blue (unvisited), navy (visited), red (active) --> - - <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" - vlink="#000080" alink="#FF0000"> - <h1 align="center">Apache Layered I/O</h1> - - <p>Layered I/O has been the holy grail of Apache module writers - for years. With Apache 2.0, module writers can finally take - advantage of layered I/O in their modules.</p> - - <p>In all previous versions of Apache, only one handler was - allowed to modify the data stream that was sent to the client. - With Apache 2.0, one module can modify the data and then - specify that other modules can modify the data if they would - like.</p> - - <h2>Taking advantage of layered I/O</h2> - - <p>In order to make a module use layered I/O, there are some - modifications 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> - - <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 will loop forever - calling the same module's handler.</p> - - <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 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, 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 client. Usually at the - end of a handler, the input (for the next module) will be the - read side of a pipe, and the output will be the write side of - the same pipe.</p> - - <h3>An Example of Layered I/O.</h3> - - <p>This example is the most basic layered I/O example possible. - It is basically CGIs generated by mod_cgi and sent to the - network via http_core.</p> - - <p>mod_cgi executes the cgi script, and then sets - request_rec->input to 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.</p> - - <p>ap_invoke_handlers() then loops back to the top of the - handler list and searches for a handler that can deal with this - content_type. In this case the correct module is the - default_handler from http_core.</p> - - <p>When default handler starts, it calls ap_setup_input, which - has found a valid request_rec->input, so that is used for - all inputs. The output field in the request_rec is NULL, so - when default_handler calls an output primitive it gets sent out - over the network.</p> - <i>Ryan Bloom, 25th March 2000</i> - </body> -</html> - diff --git a/docs/manual/sitemap.html.de b/docs/manual/sitemap.html.de index c6cf9aff1d..332cdde240 100644 --- a/docs/manual/sitemap.html.de +++ b/docs/manual/sitemap.html.de @@ -217,7 +217,6 @@ HPUX betreiben</a></li> <li><a href="developer/debugging.html">Debuggen der Speicher-Belegung in der APR </a></li> <li><a href="developer/documenting.html">Apache 2.0 dokumentieren</a></li> <li><a href="developer/hooks.html">Hook-Funktionen des Apache 2.0 </a></li> -<li><a href="developer/layeredio.html">Gestaffelte E/A des Apache 2.0</a></li> <li><a href="developer/modules.html">Module von Apache 1.3 nach Apache 2.0 konvertieren</a></li> <li><a href="developer/request.html">Verarbeitung der Anfragen im Apache 2.0</a></li> <li><a href="developer/filters.html">Wie Filter im Apache 2.0 arbeiten</a></li> diff --git a/docs/manual/sitemap.html.en b/docs/manual/sitemap.html.en index ae4f8b15b5..2264a4e2e4 100644 --- a/docs/manual/sitemap.html.en +++ b/docs/manual/sitemap.html.en @@ -217,7 +217,6 @@ Server on HPUX</a></li> <li><a href="developer/debugging.html">Debugging Memory Allocation in APR</a></li> <li><a href="developer/documenting.html">Documenting Apache 2.0</a></li> <li><a href="developer/hooks.html">Apache 2.0 Hook Functions</a></li> -<li><a href="developer/layeredio.html">Apache 2.0 Layered I/O</a></li> <li><a href="developer/modules.html">Converting Modules from Apache 1.3 to Apache 2.0</a></li> <li><a href="developer/request.html">Request Processing in Apache 2.0</a></li> <li><a href="developer/filters.html">How Filters Work in Apache 2.0</a></li> diff --git a/docs/manual/sitemap.xml b/docs/manual/sitemap.xml index 7ba5429c36..21935ca9e5 100644 --- a/docs/manual/sitemap.xml +++ b/docs/manual/sitemap.xml @@ -203,7 +203,6 @@ Server on HPUX</page> <page href="developer/debugging.html">Debugging Memory Allocation in APR</page> <page href="developer/documenting.html">Documenting Apache 2.0</page> <page href="developer/hooks.html">Apache 2.0 Hook Functions</page> -<page href="developer/layeredio.html">Apache 2.0 Layered I/O</page> <page href="developer/modules.html">Converting Modules from Apache 1.3 to Apache 2.0</page> <page href="developer/request.html">Request Processing in Apache 2.0</page> <page href="developer/filters.html">How Filters Work in Apache 2.0</page> diff --git a/docs/manual/sitemap.xml.de b/docs/manual/sitemap.xml.de index c609901582..29093cafe8 100644 --- a/docs/manual/sitemap.xml.de +++ b/docs/manual/sitemap.xml.de @@ -204,7 +204,6 @@ HPUX betreiben</page> <page href="developer/debugging.html">Debuggen der Speicher-Belegung in der APR </page> <page href="developer/documenting.html">Apache 2.0 dokumentieren</page> <page href="developer/hooks.html">Hook-Funktionen des Apache 2.0 </page> -<page href="developer/layeredio.html">Gestaffelte E/A des Apache 2.0</page> <page href="developer/modules.html">Module von Apache 1.3 nach Apache 2.0 konvertieren</page> <page href="developer/request.html">Verarbeitung der Anfragen im Apache 2.0</page> <page href="developer/filters.html">Wie Filter im Apache 2.0 arbeiten</page> |