httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wr...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/mod mod_unique_id.html
Date Wed, 26 Sep 2001 14:56:17 GMT
wrowe       01/09/26 07:56:17

  Modified:    htdocs/manual/mod mod_unique_id.html
  Log:
    Explain Multithreaded TID side effect
  
  Revision  Changes    Path
  1.8       +8 -5      httpd-docs-1.3/htdocs/manual/mod/mod_unique_id.html
  
  Index: mod_unique_id.html
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/mod_unique_id.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- mod_unique_id.html	2001/06/21 20:22:24	1.7
  +++ mod_unique_id.html	2001/09/26 14:56:17	1.8
  @@ -58,7 +58,7 @@
   
   <P>
   First a brief recap of how the Apache server works on Unix machines.
  -This feature currently isn't supported on Windows NT.  On Unix machines,
  +On Unix machines,
   Apache creates several children, the children process requests one at
   a time.  Each child can serve multiple requests in its lifetime.  For the
   purpose of this discussion, the children don't share any data
  @@ -188,9 +188,10 @@
   Afterwards they can resume requests and begin issuing the new encodings.
   
   <P>
  -This we believe is a relatively portable solution to this problem.  It can
  -be extended to multithreaded systems like Windows NT, and can grow with
  -future needs.  The identifiers generated have essentially an infinite
  +This is a relatively portable solution.  It is extended to multithreaded 
  +systems like Windows NT, which add the thread-id to the ID, producing a
  +144-bit (including 32-bit tid) quadruple that generates a 24 character
  +UNIQUE_ID value.  The identifiers generated have essentially an infinite
   life-time because future identifiers can be made longer as required.
   Essentially no communication is required between machines in the cluster
   (only NTP synchronization is required, which is low overhead), and no
  @@ -198,7 +199,9 @@
   implicit in the pid value assigned by the kernel).  In very specific
   situations the identifier can be shortened, but more information needs
   to be assumed (for example the 32-bit IP address is overkill for any
  -site, but there is no portable shorter replacement for it).
  +site, but there is no portable shorter replacement for it).  This module
  +may be extended to include an entire IPv6 address, but that is overkill 
  +for nearly all server configurations.
   
   <!--#include virtual="footer.html" -->
   </BODY>
  
  
  

Mime
View raw message