From: Jeff Trawick Date: Mon, 14 Mar 2011 21:00:31 +0000 (+0000) Subject: transformations X-Git-Tag: 2.3.12~233 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2e3c696eb401ac604a557228d2b1160af5747aae;p=thirdparty%2Fapache%2Fhttpd.git transformations git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1081561 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/developer/new_api_2_4.html.en b/docs/manual/developer/new_api_2_4.html.en index 69bcdc6b247..087f7164dfa 100644 --- a/docs/manual/developer/new_api_2_4.html.en +++ b/docs/manual/developer/new_api_2_4.html.en @@ -286,6 +286,147 @@ APLOG_MARK should only be used when calling ap_log_* without additional wrappers. In this way, the code will remain compatible with HTTPD 2.0 and 2.2.

+ +

Consider the following changes to take advantage of the new + APLOG_TRACE1..8 log levels: +

+ +

Modules sometimes add process id and/or thread id to their log + messages. These ids are now logged by default, so it may not + be necessary for the module to log them explicitly. (Users may + remove them from the error log format, but they can be + instructed to add it back if necessary for problem diagnosis.)

+ + +

If your module uses these existing APIs...

+ + +
+
ap_default_type()
+
This is no longer available; Content-Type must be configured + explicitly or added by the application.
+ +
ap_get_server_name()
+
If the returned server name is used in a URL, + use ap_get_server_name_for_url() instead. This new + function handles the odd case where the server name is an IPv6 + literal address.
+ +
ap_get_server_version()
+
For logging purposes, where detailed information is + appropriate, use ap_get_server_description(). + When generating output, where the amount of information + should be configurable by ServerTokens, use + ap_get_server_banner().
+ +
ap_graceful_stop_signalled()
+
Replace with a call + to ap_mpm_query(AP_MPMQ_MPM_STATE) and checking for + state AP_MPMQ_STOPPING.
+ +
ap_max_daemons_limit, ap_my_generation, + and ap_threads_per_child
+
Use ap_mpm_query() query codes + AP_MPMQ_MAX_DAEMON_USED, AP_MPMQ_GENERATION, + and AP_MPMQ_MAX_THREADS, respectively.
+ +
ap_mpm_query()
+
Ensure that it is not used until after the register-hooks + hook has completed. Otherwise, an MPM built as a DSO + would not have had a chance to enable support for this + function.
+ +
ap_server_conf->process->pool + userdata
+
+ Optional: +
    +
  • If your module uses this to determine which pass of the + startup hooks is being run, + use ap_state_query(AP_SQ_MAIN_STATE).
    • +
  • If your module uses this to maintain data across the + unloading and reloading of your module, use + ap_retained_data_create() and + ap_retained_data_get().
    • +
+
+ +
apr_global_mutex_create(), + apr_proc_mutex_create()
+
Optional: See ap_mutex_register(), + ap_global_mutex_create(), and + ap_proc_mutex_create(); these allow your + mutexes to be configurable with + the Mutex directive; + you can also remove any configuration mechanisms in your + module for such mutexes +
+ +
CORE_PRIVATE
+
This is now unnecessary and ignored.
+ +
dav_new_error() + and dav_new_error_tag()
+
Previously, these assumed that errno contained + information describing the failure. Now, + an apr_status_t parameter must be provided. Pass + 0/APR_SUCCESS if there is no such error information, or a valid + apr_status_t value otherwise.
+ +
unixd_config
+
This has been renamed to ap_unixd_config.
+
+ + +

If your module interfaces with this feature...

+ +
+
suEXEC
+
Optional: If your module logs an error + when ap_unixd_config.suexec_enabled is 0, + also log the value of the new + field suexec_disabled_reason, which contains an + explanation of why it is not available.
+ +
Extended status data in the scoreboard
+
In previous releases, ExtendedStatus had to be + set to On, which in turn required that + mod_status was loaded. In 2.4, just + set ap_extended_status to 1 in a + pre-config hook and the extended status data will be + available.
+ +
+ + +

Does your module...

+ +
Parse query args
+
Consider if ap_args_to_table() would be + helpful.
+ +
Parse form data...
+
Use ap_parse_form_data().
+ +
Check for request header fields Content-Length + and Transfer-Encoding to see if a body was + specified
+
Use ap_request_has_body().
+ +
Implement cleanups which clear pointer variables
+
Use ap_pool_cleanup_set_null().
diff --git a/docs/manual/mod/directives.html.en b/docs/manual/mod/directives.html.en index 1a6f7491f20..28d90eb73fc 100644 --- a/docs/manual/mod/directives.html.en +++ b/docs/manual/mod/directives.html.en @@ -289,6 +289,7 @@
  • LanguagePriority
  • LDAPCacheEntries
  • LDAPCacheTTL
    • +
  • LDAPConnectionPoolTTL
  • LDAPConnectionTimeout
  • LDAPLibraryDebug
  • LDAPOpCacheEntries
    • diff --git a/docs/manual/mod/mod_cache.xml.ja b/docs/manual/mod/mod_cache.xml.ja index b276a4f0b59..bbaef549ab5 100644 --- a/docs/manual/mod/mod_cache.xml.ja +++ b/docs/manual/mod/mod_cache.xml.ja @@ -1,7 +1,7 @@ - + + +Shared Object Cache in Apache HTTP Server - Apache HTTP Server + + + + +
    +

    Modules | Directives | FAQ | Glossary | Sitemap

    +

    Apache HTTP Server Version 2.3

    +
    +
    <-
    +
    +Apache > HTTP Server > Documentation > Version 2.3

    Shared Object Cache in Apache HTTP Server

    +
    +

    Available Languages:  en 

    +
    + +

    The Shared Object Cache provides a means to share simple data + across all a server's workers, regardless of thread + and process models. It is used where the advantages of sharing + data across processes outweigh the performance overhead of + inter-process communication.

    +
    +
    top
    +
    +

    Shared Object Cache Providers

    + +

    The shared object cache as such is an abstraction. Four different + modules implement it. To use the cache, one or more of these modules + must be present, and configured.

    +

    The only configuration required is to select which cache provider + to use. This is the responsibility of modules using the cache, and + they enable selecton using directives such as + AuthnCacheSOCache, + SSLSessionCache, and + SSLStaplingCache.

    +

    Currently available providers are:

    +
    +
    "dbm" (mod_socache_dbm)
    +
    This makes use of a DBM hash file. + The choice of underlying DBM configuration may be configurable + if the installed APR version supports multiple DBM implementations.
    +
    "dc" (mod_socache_dc)
    +
    This makes use of the distcache + distributed session caching libraries.
    +
    "mc" (mod_socache_memcache)
    +
    This makes use of the memcached + high-performance, distributed memory object caching system.
    +
    "shmcb" (mod_socache_shmcb)
    +
    This makes use of a high-performance cyclic buffer inside a + shared memory segment.
    +
    +
    +
    +

    Available Languages:  en 

    +
    + \ No newline at end of file