Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Added a FAQ entry about thread safety based on a paragraph suggested by John Yu.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@138944 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Robert Burrell Donkin
2002-12-12 19:56:44 +00:00
parent 6daa5b9439
commit 4f6bc55f0e
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
usersguide.html
View File

@@ -28,6 +28,8 @@ Table of Contents</h3>
<br><a href="#Integration">Integration</a> <br><a href="#Integration">Integration</a>
<br>&nbsp; <a href="#Mechanism">Mechanism</a> <br>&nbsp; <a href="#Mechanism">Mechanism</a>
<br>&nbsp; <a href="#Configuring the Logger Implementation">Configuring the Logger Implementation</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>
<h2> <h2>
<a NAME="Introduction"></a>Introduction</h2> <a NAME="Introduction"></a>Introduction</h2>
@@ -439,6 +441,13 @@ For example: one can capture DEBUG (and higher) level information in a logfile,
while limiting console output to INFO (and higher). while limiting console output to INFO (and higher).
</ul> </ul>
<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>
</body> </body>
</html> </html>