code will remain compatible with HTTPD 2.0 and 2.2.</p>
<p>Consider the following changes to take advantage of the new
- <code>APLOG_TRACE1..8</code> log levels:
+ <code>APLOG_TRACE1..8</code> log levels:</p>
<ul>
<li>Check current use of <code>APLOG_DEBUG</code> and
consider if one of the <code>APLOG_TRACEn</code> levels is
configured log level, use the <code>APLOGtrace<em>n</em></code>
and <code>APLOGrtrace<em>n</em></code> macros to first check
if tracing is enabled.</li>
- </ul></p>
+ </ul>
<p>Modules sometimes add process id and/or thread id to their log
messages. These ids are now logged by default, so it may not
<section id="upgrading_newfeatures">
<title>Does your module...</title>
+ <dl>
<dt>Parse query args</dt>
<dd>Consider if <code>ap_args_to_table()</code> would be
helpful.</dd>
<dt>Implement cleanups which clear pointer variables</dt>
<dd>Use <code>ap_pool_cleanup_set_null()</code>.</dd>
+ </dl>
</section>
</section>
<description>Discard backend connections that have been sitting in the connection pool too long</description>
<syntax>LDAPConnectionPoolTTL <var>n</var></syntax>
<default>LDAPConnectionPoolTTL -1</default>
-<compatability>Apache HTTP Server 2.3.12 and later</compatability>
<contextlist><context>server config</context><context>virtual host</context></contextlist>
+<compatibility>Apache HTTP Server 2.3.12 and later</compatibility>
<usage>
<p>Specifies the maximum age, in seconds, that a pooled LDAP connection can remain idle