[slf4j-dev] svn commit: r1318 - slf4j/trunk/slf4j-site/src/site/pages

[ravn at slf4j.org]

Author: ravn
Date: Sat Apr 18 21:20:52 2009
New Revision: 1318

Modified:
   slf4j/trunk/slf4j-site/src/site/pages/manual.html

Log:
merged logback mentioning


Modified: slf4j/trunk/slf4j-site/src/site/pages/manual.html
==============================================================================
--- slf4j/trunk/slf4j-site/src/site/pages/manual.html	(original)
+++ slf4j/trunk/slf4j-site/src/site/pages/manual.html	Sat Apr 18 21:20:52 2009
@@ -141,9 +141,15 @@
       </dl>
 
       <p>There are also SLF4J bindings external to the SLF4J project,
-      e.g. <a href="http://logback.qos.ch/">logback</a>.
+      e.g. <a href="http://logback.qos.ch/">logback</a>, where the
+      <a href="http://logback.qos.ch/apidocs/ch/qos/logback/classic/Logger.html">
+      <code>ch.qos.logback.classic.Logger</code></a> class in
+      logback-classic directly implements SLF4J's
+      <a href="http://www.slf4j.org/apidocs/org/slf4j/Logger.html">
+      <code>org.slf4j.Logger</code></a> interface.
       </p>
 
+
       <p>To switch logging frameworks, just replace slf4j bindings on
       your class path. For example, to switch from java.util.logging
       to log4j, just replace slf4j-jdk14-${project.version}.jar with
@@ -191,26 +197,6 @@
       another on the class path and restarting the application.  This
       approach has proven to be simple and very robust.
       </p>
-     
-        
-      <h3>Built-in support in logback</h3>
-
-      <p>The <a href="http://logback.qos.ch/apidocs/ch/qos/logback/classic/Logger.html">
-      <code>ch.qos.logback.classic.Logger</code></a> class in
-      logback directly implements SLF4J's
-      <a href="http://www.slf4j.org/apidocs/org/slf4j/Logger.html">
-      <code>org.slf4j.Logger</code></a> interface.
-      </p>
-
-      <p>Logback's built-in (a.k.a. native) support for SLF4J means
-      that the adapter for does not need to wrap logback objects in
-      order to make them conform to SLF4J's <code>Logger</code>
-      interface. A logback <code>ch.qos.logback.classic.Logger</code>
-      <em>is</em> a <code>org.slf4j.Logger</code>. Thus, using SLF4J
-      in conjunction with logback involves strictly zero memory and
-      computational overhead.
-      </p>
-
         
       <h3><a name="mdc" href="#mdc">Mapped Diagnostic Context (MDC)
       support</a></h3>