httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yosh...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/developer hooks.html.en hooks.xml
Date Mon, 14 Jul 2003 06:18:03 GMT
yoshiki     2003/07/13 23:18:03

  Modified:    docs/manual/developer hooks.html.en hooks.xml
  Log:
  The name of HOOK_ORDER is changed to APR_HOOK_ORDER.
  
  Revision  Changes    Path
  1.6       +10 -10    httpd-2.0/docs/manual/developer/hooks.html.en
  
  Index: hooks.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/developer/hooks.html.en,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- hooks.html.en	29 May 2003 16:12:50 -0000	1.5
  +++ hooks.html.en	14 Jul 2003 06:18:02 -0000	1.6
  @@ -170,7 +170,7 @@
           static void my_register_hooks()<br />
           {<br />
           <span class="indent">
  -          ap_hook_do_something(my_something_doer, NULL, NULL, HOOK_MIDDLE);<br />
  +          ap_hook_do_something(my_something_doer, NULL, NULL, APR_HOOK_MIDDLE);<br />
           </span>
           }<br />
           <br />
  @@ -190,19 +190,19 @@
         There are two mechanisms for doing this. The first, rather
         crude, method, allows us to specify roughly where the hook is
         run relative to other modules. The final argument control this.
  -      There are three possible values: <code>HOOK_FIRST</code>,
  -      <code>HOOK_MIDDLE</code> and <code>HOOK_LAST</code>.</p>
  +      There are three possible values: <code>APR_HOOK_FIRST</code>,
  +      <code>APR_HOOK_MIDDLE</code> and <code>APR_HOOK_LAST</code>.</p>
   
         <p>All modules using any particular value may be run in any
         order relative to each other, but, of course, all modules using
  -      <code>HOOK_FIRST</code> will be run before <code>HOOK_MIDDLE</code>
  -      which are before <code>HOOK_LAST</code>. Modules that don't care
  -      when they are run should use <code>HOOK_MIDDLE</code>. <em>(I spaced
  -      these out so people could do stuff like <code>HOOK_FIRST-2</code>
  +      <code>APR_HOOK_FIRST</code> will be run before <code>APR_HOOK_MIDDLE</code>
  +      which are before <code>APR_HOOK_LAST</code>. Modules that don't care
  +      when they are run should use <code>APR_HOOK_MIDDLE</code>. <em>(I
spaced
  +      these out so people could do stuff like <code>APR_HOOK_FIRST-2</code>
         to get in slightly earlier, but is this wise? - Ben)</em></p>
   
         <p>Note that there are two more values,
  -      <code>HOOK_REALLY_FIRST</code> and <code>HOOK_REALLY_LAST</code>.
These
  +      <code>APR_HOOK_REALLY_FIRST</code> and <code>APR_HOOK_REALLY_LAST</code>.
These
         should only be used by the hook exporter.</p>
   
         <p>The other method allows finer control. When a module knows
  @@ -219,13 +219,13 @@
           <span class="indent">
             static const char * const aszPre[] = { "mod_xyz.c", "mod_abc.c", NULL };<br
/>
             <br />
  -          ap_hook_do_something(my_something_doer, aszPre, NULL, HOOK_MIDDLE);<br />
  +          ap_hook_do_something(my_something_doer, aszPre, NULL, APR_HOOK_MIDDLE);<br
/>
           </span>
           }
         </code></p></div>
   
         <p>Note that the sort used to achieve this is stable, so
  -      ordering set by <code>HOOK_<var>ORDER</var></code> is preserved,
as far
  +      ordering set by <code>APR_HOOK_<var>ORDER</var></code> is
preserved, as far
         as is possible.</p>
   
         <p class="cite"><cite>Ben Laurie</cite>, 15th August 1999</p>
  
  
  
  1.5       +10 -10    httpd-2.0/docs/manual/developer/hooks.xml
  
  Index: hooks.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/developer/hooks.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- hooks.xml	12 Apr 2003 15:04:45 -0000	1.4
  +++ hooks.xml	14 Jul 2003 06:18:02 -0000	1.5
  @@ -153,7 +153,7 @@
           static void my_register_hooks()<br />
           {<br />
           <indent>
  -          ap_hook_do_something(my_something_doer, NULL, NULL, HOOK_MIDDLE);<br />
  +          ap_hook_do_something(my_something_doer, NULL, NULL, APR_HOOK_MIDDLE);<br />
           </indent>
           }<br />
           <br />
  @@ -173,19 +173,19 @@
         There are two mechanisms for doing this. The first, rather
         crude, method, allows us to specify roughly where the hook is
         run relative to other modules. The final argument control this.
  -      There are three possible values: <code>HOOK_FIRST</code>,
  -      <code>HOOK_MIDDLE</code> and <code>HOOK_LAST</code>.</p>
  +      There are three possible values: <code>APR_HOOK_FIRST</code>,
  +      <code>APR_HOOK_MIDDLE</code> and <code>APR_HOOK_LAST</code>.</p>
   
         <p>All modules using any particular value may be run in any
         order relative to each other, but, of course, all modules using
  -      <code>HOOK_FIRST</code> will be run before <code>HOOK_MIDDLE</code>
  -      which are before <code>HOOK_LAST</code>. Modules that don't care
  -      when they are run should use <code>HOOK_MIDDLE</code>. <em>(I spaced
  -      these out so people could do stuff like <code>HOOK_FIRST-2</code>
  +      <code>APR_HOOK_FIRST</code> will be run before <code>APR_HOOK_MIDDLE</code>
  +      which are before <code>APR_HOOK_LAST</code>. Modules that don't care
  +      when they are run should use <code>APR_HOOK_MIDDLE</code>. <em>(I
spaced
  +      these out so people could do stuff like <code>APR_HOOK_FIRST-2</code>
         to get in slightly earlier, but is this wise? - Ben)</em></p>
   
         <p>Note that there are two more values,
  -      <code>HOOK_REALLY_FIRST</code> and <code>HOOK_REALLY_LAST</code>.
These
  +      <code>APR_HOOK_REALLY_FIRST</code> and <code>APR_HOOK_REALLY_LAST</code>.
These
         should only be used by the hook exporter.</p>
   
         <p>The other method allows finer control. When a module knows
  @@ -202,13 +202,13 @@
           <indent>
             static const char * const aszPre[] = { "mod_xyz.c", "mod_abc.c", NULL };<br
/>
             <br />
  -          ap_hook_do_something(my_something_doer, aszPre, NULL, HOOK_MIDDLE);<br />
  +          ap_hook_do_something(my_something_doer, aszPre, NULL, APR_HOOK_MIDDLE);<br
/>
           </indent>
           }
         </example>
   
         <p>Note that the sort used to achieve this is stable, so
  -      ordering set by <code>HOOK_<var>ORDER</var></code> is preserved,
as far
  +      ordering set by <code>APR_HOOK_<var>ORDER</var></code> is
preserved, as far
         as is possible.</p>
   
         <p class="cite"><cite>Ben Laurie</cite>, 15th August 1999</p>
  
  
  

Mime
View raw message