From 9bcbfdc46ca4787ecdc814e72f4f35ddc8f02e19 Mon Sep 17 00:00:00 2001 From: Cliff Woolley Date: Wed, 27 Jun 2001 18:44:20 +0000 Subject: [PATCH] It's apr_pool_t, not apr_pools_t. And tables are in APR's namespace, not Apache's, so it's apr_table_t and not ap_table_t. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89434 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/developer/modules.html | 17 +++++++---------- docs/manual/developer/modules.html.en | 17 +++++++---------- 2 files changed, 14 insertions(+), 20 deletions(-) diff --git a/docs/manual/developer/modules.html b/docs/manual/developer/modules.html index 6237f961ea..7d6c27c3d9 100644 --- a/docs/manual/developer/modules.html +++ b/docs/manual/developer/modules.html @@ -35,21 +35,18 @@ These now need to be of type ap_status_t and return a value of that type. Norma These should now be renamed to better signify where they sit in the overall process. So the name gets a small change from mmap_init to mmap_post_config. The arguments passed have undergone a radical change and now look like

-

-Throughout Apache the old pools have been replced by the apr_pools_t, though their use remains remarkably similar. -

Data Types

A lot of the data types have been moved into the APR. This means that some have had a name change, such as the one shown above. The following is a brief list of some of the changes that you are likely to have to make.

@@ -61,7 +58,7 @@ The messier changes... The new architecture uses a series of hooks to provide for calling your functions. These you'll need to add to your module by way of a new function, static void register_hooks(void). The function is really reasonably straightforward once you understand what needs to be done. Each function that needs calling at some stage in the processing of a request needs to be registered, handlers do not. There are a number of phases where functions can be added, and for each you can specify with a high degree of control the relative order that the function will be called in.

-This is the code that was added to mod_mmap_static +This is the code that was added to mod_mmap_static: 

 static void register_hooks(void)
@@ -156,7 +153,7 @@ The stages that read directly across :
 /* merge server config */ ==> /* merge per-server config structures     */
 
 
  • 
-/* command table */ ==> /* command ap_table_t */
+/* command table */ ==> /* command apr_table_t */
 
    • 
 
  • 
 /* handlers */ ==> /* handlers */
diff --git a/docs/manual/developer/modules.html.en b/docs/manual/developer/modules.html.en
index 6237f961ea..7d6c27c3d9 100644
--- a/docs/manual/developer/modules.html.en
+++ b/docs/manual/developer/modules.html.en
@@ -35,21 +35,18 @@ These now need to be of type ap_status_t and return a value of that type.  Norma
 These should now be renamed to better signify where they sit in the overall process.  So the name gets a small change from mmap_init to mmap_post_config.  The arguments passed have undergone a radical change and now look like
 
    
 
      
-
    • apr_pools_t *p,
      • 
-
    • apr_pools_t *plog,
      • 
-
    • apr_pools_t *ptemp,
      • 
+
    • apr_pool_t *p,
      • 
+
    • apr_pool_t *plog,
      • 
+
    • apr_pool_t *ptemp,
      • 
 
    • server_rec *s
      • 
 
    
-
    
-Throughout Apache the old pools have been replced by the apr_pools_t, though their use remains remarkably similar.
-
    
 
 
    Data Types
    
 
    
 A lot of the data types have been moved into the APR.  This means that some have had a name change, such as the one shown above.  The following is a brief list of some of the changes that you are likely to have to make.
 
      
-
    • pool becomes apr_pools_t
      • 
-
    • table becomes ap_table_t
      • 
+
    • pool becomes apr_pool_t
      • 
+
    • table becomes apr_table_t
      • 
 
    
 
    
 
@@ -61,7 +58,7 @@ The messier changes...
 The new architecture uses a series of hooks to provide for calling your functions.  These you'll need to add to your module by way of a new function, static void register_hooks(void).  The function is really reasonably straightforward once you understand what needs to be done.  Each function that needs calling at some stage in the processing of a request needs to be registered, handlers do not.  There are a number of phases where functions can be added, and for each you can specify with a high degree of control the relative order that the function will be called in.
 
    
 
    
-This is the code that was added to mod_mmap_static
+This is the code that was added to mod_mmap_static:
 
    
 
     static void register_hooks(void)
@@ -156,7 +153,7 @@ The stages that read directly across :
 /* merge server config */ ==> /* merge per-server config structures     */
 
    • 
 
  • 
-/* command table */ ==> /* command ap_table_t */
+/* command table */ ==> /* command apr_table_t */
 
    • 
 
  • 
 /* handlers */ ==> /* handlers */
-- 
2.50.1