From 6523d8eeab77a032b4bf3bef5b2829aeff403ce6 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Thu, 15 Aug 2002 23:24:34 +0000 Subject: [PATCH] New XML. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96392 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mpm.html.en | 69 +++++++++++++---------------- docs/manual/mpm.xml | 96 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 125 insertions(+), 40 deletions(-) create mode 100644 docs/manual/mpm.xml diff --git a/docs/manual/mpm.html.en b/docs/manual/mpm.html.en index db67792034d..72505f60d26 100644 --- a/docs/manual/mpm.html.en +++ b/docs/manual/mpm.html.en @@ -1,19 +1,11 @@ - - - - - - - Apache Multi-Processing Modules (MPMs) - - - - - - -

Apache Multi-Processing Modules

+Multi-Processing Modules (MPMs) - Apache HTTP Server
[APACHE DOCUMENTATION]

Apache HTTP Server Version 2.0

Multi-Processing Modules (MPMs)

+

This document describes what a Multi-Processing Module is and +how they are using by the Apache HTTP Server.

+

Introduction

The Apache HTTP Server is designed to be a powerful and flexible web server that can work on a very wide variety of @@ -38,20 +30,20 @@

@@ -60,7 +52,7 @@ be loaded into the server at any time. The list of available MPMs appears on the module index page.

-

Choosing an MPM

+

Choosing an MPM

MPMs must be chosen during configuration, and compiled into the server. Compilers are capable of optimizing a lot of @@ -77,19 +69,16 @@ determine which MPM was chosen by using ./httpd -l. This command will list every module that is compiled into the server, including the MPM.

- -

MPM Defaults

- - - - - - +

MPM Defaults

+ +

The following table lists the default MPMs for various operating +systems. This will be the MPM selected if you do not make another +choice at compile-time.

+ + + + + + +
BeOSbeos
OS/2mpmt_os2
Unixprefork
Windowsmpm_winnt
+

Apache HTTP Server Version 2.0

IndexHome \ No newline at end of file diff --git a/docs/manual/mpm.xml b/docs/manual/mpm.xml new file mode 100644 index 00000000000..8c40a9f98ee --- /dev/null +++ b/docs/manual/mpm.xml @@ -0,0 +1,96 @@ + + + + + + + Multi-Processing Modules (MPMs) + + +

This document describes what a Multi-Processing Module is and +how they are using by the Apache HTTP Server.

+ + +
Introduction + +

The Apache HTTP Server is designed to be a powerful and + flexible web server that can work on a very wide variety of + platforms in a range of different environments. Different + platforms and different environments often require different + features, or may have different ways of implementing the same + feature most efficiently. Apache has always accommodated a wide + variety of environments through its modular design. This design + allows the webmaster to choose which features will be included + in the server by selecting which modules to load either at + compile-time or at run-time.

+ +

Apache 2.0 extends this modular design to the most basic + functions of a web server. The server ships with a selection of + Multi-Processing Modules (MPMs) which are responsible for + binding to network ports on the machine, accepting requests, + and dispatching children to handle the requests.

+ +

Extending the modular design to this level of the server + allows two important benefits:

+ +
    +
  • Apache can more cleanly and efficiently support a wide + variety of operating systems. In particular, the Windows + version of Apache is now much more efficient, since + mpm_winnt can use native + networking features in place of the POSIX layer used in + Apache 1.3. This benefit also extends to other operating + systems that implement specialized MPMs.
    • + +
  • The server can be better customized for the needs of the + particular site. For example, sites that need a great deal of + scalability can choose to use a threaded MPM like + worker, while sites requiring + stability or compatibility with older software can use a + prefork. In addition, + special features like serving different hosts under different + userids (perchild) can be + provided.
    • +
+ +

At the user level, MPMs appear much like other Apache + modules. The main difference is that one and only one MPM must + be loaded into the server at any time. The list of available + MPMs appears on the module index page.

+ +
+ +
Choosing an MPM + +

MPMs must be chosen during configuration, and compiled into + the server. Compilers are capable of optimizing a lot of + functions if threads are used, but only if they know that + threads are being used. Because some MPMs use threads on Unix + and others don't, Apache will always perform better if the MPM + is chosen at configuration time and built into Apache.

+ +

To actually choose the desired MPM, use the argument + --with-mpm= NAME with the ./configure script. + NAME is the name of the desired MPM.

+ +

Once the server has been compiled, it is possible to + determine which MPM was chosen by using ./httpd + -l. This command will list every module that is compiled + into the server, including the MPM.

+
+ +
MPM Defaults + +

The following table lists the default MPMs for various operating +systems. This will be the MPM selected if you do not make another +choice at compile-time.

+ + + + + + +
BeOSbeos
OS/2mpmt_os2
Unixprefork
Windowsmpm_winnt
+
+ + -- 2.47.3