<p>The second way is to compile the module as a DLL, a shared
library that can be loaded into the server at runtime, using
- the <code><directive>LoadModule</directive></code>
+ the <directive>LoadModule</directive>
directive. These module DLLs can be distributed and run on any
Apache httpd for Windows installation, without recompilation of the
server.</p>
<usage>
- <p>The LoadFile directive links in the named object files or
+ <p>The <directive>LoadFile</directive> directive links in the named object files or
libraries when the server is started or restarted; this is used
to load additional code which may be required for some module
to work. <em>Filename</em> is either an absolute path or
</contextlist>
<usage>
- <p>The LoadModule directive links in the object file or library
+ <p>The <directive>LoadModule</directive> directive links in the object file or library
<em>filename</em> and adds the module structure named
<em>module</em> to the list of active modules. <em>Module</em>
is the name of the external variable of type
<code>module</code> in the file, and is listed as the <a
href="module-dict.html#ModuleIdentifier">Module Identifier</a>
- in the module documentation. Example:</p>
+ in the module documentation.</p>
+
+ <p>For example:</p>
<highlight language="config">
LoadModule status_module "modules/mod_status.so"