httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jwool...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/developer modules.html
Date Wed, 27 Jun 2001 18:44:23 GMT
jwoolley    01/06/27 11:44:22

  Modified:    docs/manual/developer modules.html
  Log:
  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.
  
  Revision  Changes    Path
  1.4       +7 -10     httpd-2.0/docs/manual/developer/modules.html
  
  Index: modules.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/developer/modules.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -d -u -r1.3 -r1.4
  --- modules.html	2001/06/27 03:34:15	1.3
  +++ modules.html	2001/06/27 18:44:20	1.4
  @@ -35,21 +35,18 @@
   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
   </p>
   <ul style="list-style:none">
  -<li>apr_pools_t *p,</li>
  -<li>apr_pools_t *plog,</li>
  -<li>apr_pools_t *ptemp,</li>
  +<li>apr_pool_t *p,</li>
  +<li>apr_pool_t *plog,</li>
  +<li>apr_pool_t *ptemp,</li>
   <li>server_rec *s</li>
   </ul>
  -<p>
  -Throughout Apache the old pools have been replced by the apr_pools_t, though their use
remains remarkably similar.
  -</p>
   
   <h3>Data Types</h3>
   <p>
   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.
   <ul style="list-style:none">
  -<li>pool becomes apr_pools_t</li>
  -<li>table becomes ap_table_t</li>
  +<li>pool becomes apr_pool_t</li>
  +<li>table becomes apr_table_t</li>
   </ul>
   <hr>
   
  @@ -61,7 +58,7 @@
   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.
   </p>
   <p>
  -This is the code that was added to mod_mmap_static
  +This is the code that was added to mod_mmap_static:
   </p>
   <pre>
   static void register_hooks(void)
  @@ -156,7 +153,7 @@
   /* merge server config */ ==> /* merge per-server config structures     */
   </li>
   <li>
  -/* command table */ ==> /* command ap_table_t */
  +/* command table */ ==> /* command apr_table_t */
   </li>
   <li>
   /* handlers */ ==> /* handlers */
  
  
  

Mime
View raw message