commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons/logging usersguide.html
Date Thu, 12 Dec 2002 19:56:45 GMT
rdonkin     2002/12/12 11:56:45

  Modified:    logging  usersguide.html
  Added a FAQ entry about thread safety based on a paragraph suggested by John Yu.
  Revision  Changes    Path
  1.4       +9 -0      jakarta-commons/logging/usersguide.html
  Index: usersguide.html
  RCS file: /home/cvs/jakarta-commons/logging/usersguide.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- usersguide.html	23 Aug 2002 14:55:32 -0000	1.3
  +++ usersguide.html	12 Dec 2002 19:56:44 -0000	1.4
  @@ -28,6 +28,8 @@
   <br><a href="#Integration">Integration</a>
   <br>&nbsp; <a href="#Mechanism">Mechanism</a>
   <br>&nbsp; <a href="#Configuring the Logger Implementation">Configuring
the Logger Implementation</a>
  +<br><a href="#FAQ">Frequently Asked Questions</a>
  +<br>&nbsp; <a href="#Thread Safety">Is JCL Thread Safe?</a>
   <a NAME="Introduction"></a>Introduction</h2>
  @@ -439,6 +441,13 @@
   while limiting console output to INFO (and higher).
  +<h2><a NAME="FAQ">Frequently Asked Questions</a></h2>
  +<h3><a NAME="Thread Safety">Is JCL Thread Safe?</a></h3>
  +<p> JCL doesn't (and cannot) impose any requirement on thread safety on the underlying
implementation and thus its SPI contract doesn't guarantee thread safety. However, JCL can
be safely used a multi-threaded environment as long as the underlying implementation is thread-safe.</p>
  +<p>It would be very unusual for a logging system to be thread unsafe. Certainly,
JCL is thread safe when used with the distributed Log implementations.</p>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message