diff --git a/docs/manual/mod/mod_so.xml b/docs/manual/mod/mod_so.xml index 2c510b9249..df00229d87 100755 --- a/docs/manual/mod/mod_so.xml +++ b/docs/manual/mod/mod_so.xml @@ -1,16 +1,17 @@ + mod_so -Base (Windows>; Optional (Unix) -so_module -mod_so.c -Available in Apache 1.3 and later. - -This module provides for loading of executable code and -modules into the server at start-up or restart time. + This module provides for loading of executable code and + modules into the server at start-up or restart time. + +Base (Windows>; Optional (Unix) +mod_so.c +so_module +Available in Apache 1.3 and later. @@ -20,8 +21,8 @@ modules into the server at start-up or restart time. rather than requiring a recompilation.

On Unix, the loaded code typically comes from shared object - files (usually with .so extension), on Windows - this may either the .so or .dll + files (usually with .so extension), on Windows + this may either the .so or .dll extension. This module is only available in Apache 1.3 and up.

@@ -30,21 +31,23 @@ modules into the server at start-up or restart time. Windows, mod_dll was used in beta release 1.3b1 through 1.3b5. mod_so combines these two modules into a single module for all operating systems.

- -

Warning: Apache 1.3 modules cannot be directly used + Warning +

Apache 1.3 modules cannot be directly used with Apache 2.0 - the module must be modified to dynamically - load or compile into Apache 2.0.

+ load or compile into Apache 2.0.

+
-
Creating Loadable Modules -for Windows +
Creating Loadable Modules for Windows -

Note: the module name format changed for Windows + Note +

The module name format changed for Windows with Apache 1.3.15 and 2.0 - the modules are now named as - mod_foo.so. While mod_so still loads modules with + mod_foo.so

+

While mod_so still loads modules with ApacheModuleFoo.dll names, the new naming convention is preferred; if you are converting your loadable module for 2.0, - please fix the name to this 2.0 convention.

+ please fix the name to this 2.0 convention.

The Apache module API is unchanged between the Unix and Windows versions. Many modules will run on Windows with no or @@ -100,7 +103,7 @@ for Windows .dsp.

This should create a DLL version of your module. Now simply - place it in the modules directory of your server + place it in the modules directory of your server root, and use the LoadModule directive to load it.

@@ -108,12 +111,12 @@ for Windows LoadFile +Link in the named object file or library LoadFile filename [filename] ... none server config -Link in the named object file or library @@ -127,13 +130,13 @@ for Windows LoadModule +Links in the object file or library, and adds to the list +of active modules LoadModule module filename none server config -Links in the object file or library, and adds to the list -of active modules

The LoadModule directive links in the object file or library