httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bri...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/developer thread_safety.html
Date Fri, 16 Aug 2002 00:12:16 GMT
brianp      2002/08/15 17:12:16

  Modified:    docs/manual/developer thread_safety.html
  Log:
  Minor copy editing
  
  Revision  Changes    Path
  1.3       +3 -3      httpd-2.0/docs/manual/developer/thread_safety.html
  
  Index: thread_safety.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/developer/thread_safety.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- thread_safety.html	16 Aug 2002 00:01:29 -0000	1.2
  +++ thread_safety.html	16 Aug 2002 00:12:16 -0000	1.3
  @@ -5,7 +5,7 @@
     <head>
       <meta name="generator" content="HTML Tidy, see www.w3.org" />
   
  -    <title>Apache 2.0 Thread Safe Issues</title>
  +    <title>Apache 2.0 Thread Safety Issues</title>
     </head>
     <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
   
  @@ -13,9 +13,9 @@
     vlink="#000080" alink="#FF0000">
       <!--#include virtual="header.html" -->
   
  -    <h1>Thread Safetyness</h1>
  +    <h1>Thread Safety</h1>
       <p>When using any of the threaded mpms in Apache 2.0 it is important
  -    that every function from Apache be thread safe.  When linking in 3rd
  +    that every function called from Apache be thread safe.  When linking in 3rd
       party extensions it can be difficult to determine whether the resulting
       server will be thread safe.  Casual testing generally won't tell you this
       either as thread safety problems can lead to subtle race conditons that
  
  
  

Mime
View raw message