From: Rich Bowen Date: Thu, 13 Jan 2011 14:48:21 +0000 (+0000) Subject: Rebuild transformations and translations. X-Git-Tag: 2.3.11~230 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0cfd4b9be09522940b1374038855c2ebe8e96c04;p=apache Rebuild transformations and translations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1058589 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/dso.html.en b/docs/manual/dso.html.en index e10697c4f4..279694a634 100644 --- a/docs/manual/dso.html.en +++ b/docs/manual/dso.html.en @@ -56,7 +56,7 @@ core which cannot be put into a DSO itself. Practically all other distributed Apache httpd modules will then be placed into a DSO. After a module is compiled into a DSO named - mod_foo.so you can use mod_so's LoadModule command in your + mod_foo.so you can use mod_so's LoadModule directive in your httpd.conf file to load this module at server startup or restart.

The DSO builds for individual modules can be disabled via @@ -132,13 +132,13 @@ $ apxs -cia mod_foo.c

Background

-

On modern Unix derivatives there exists a nifty mechanism - usually called dynamic linking/loading of Dynamic Shared +

On modern Unix derivatives there exists a mechanism + called dynamic linking/loading of Dynamic Shared Objects (DSO) which provides a way to build a piece of program code in a special format for loading it at run-time into the address space of an executable program.

-

This loading can usually be done in two ways: Automatically +

This loading can usually be done in two ways: automatically by a system program called ld.so when an executable program is started or manually from within the executing program via a programmatic system interface to the @@ -217,8 +217,7 @@ $ apxs -cia mod_foo.c

The shared library approach is the typical one, because it is what the DSO mechanism was designed for, hence it is used for nearly all types of libraries the operating system - provides. On the other hand using shared objects for extending - a program is not used by a lot of programs.

+ provides.

top
@@ -229,23 +228,22 @@ $ apxs -cia mod_foo.c
  • The server package is more flexible at run-time because - the actual server process can be assembled at run-time via + the server process can be assembled at run-time via LoadModule - httpd.conf configuration commands instead of - configure options at build-time. For instance + httpd.conf configuration directives instead of + configure options at build-time. For instance, this way one is able to run different server instances - (standard & SSL version, minimalistic & powered up - version [mod_perl, PHP3], etc.) with only one Apache httpd + (standard & SSL version, minimalistic & dynamic + version [mod_perl, mod_php], etc.) with only one Apache httpd installation.
  • The server package can be easily extended with - third-party modules even after installation. This is at least - a great benefit for vendor package maintainers who can create - a Apache httpd core package and additional packages containing - extensions like PHP, mod_perl, mod_security, - etc.
    • + third-party modules even after installation. This is + a great benefit for vendor package maintainers, who can create + an Apache httpd core package and additional packages containing + extensions like PHP, mod_perl, mod_security, etc. -
  • Easier Apache httpd module prototyping because with the +
  • Easier Apache httpd module prototyping, because with the DSO/apxs pair you can both work outside the Apache httpd source tree and only need an apxs -i command followed by an apachectl restart to @@ -256,18 +254,14 @@ $ apxs -cia mod_foo.c

    DSO has the following disadvantages:

      -
    • The DSO mechanism cannot be used on every platform - because not all operating systems support dynamic loading of - code into the address space of a program.
      • -
    • The server is approximately 20% slower at startup time because of the symbol resolving overhead the Unix loader now has to do.
    • The server is approximately 5% slower at execution time - under some platforms because position independent code (PIC) + under some platforms, because position independent code (PIC) sometimes needs complicated assembler tricks for relative - addressing which are not necessarily as fast as absolute + addressing, which are not necessarily as fast as absolute addressing.
    • Because DSO modules cannot be linked against other diff --git a/docs/manual/dso.xml.ja b/docs/manual/dso.xml.ja index 6636ca45c2..4a7d1345aa 100644 --- a/docs/manual/dso.xml.ja +++ b/docs/manual/dso.xml.ja @@ -1,7 +1,7 @@ - + + + +