[logback-dev] svn commit: r2123 - in logback/trunk/logback-site/src/site/pages: . manual

[noreply.ceki at qos.ch]

Author: ceki
Date: Fri Jan  9 18:46:02 2009
New Revision: 2123

Modified:
   logback/trunk/logback-site/src/site/pages/manual/appenders.html
   logback/trunk/logback-site/src/site/pages/news.html

Log:
- Fixed LBSITE-23
- added blurb in the news about ViewStatusServlet

Modified: logback/trunk/logback-site/src/site/pages/manual/appenders.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/manual/appenders.html	(original)
+++ logback/trunk/logback-site/src/site/pages/manual/appenders.html	Fri Jan  9 18:46:02 2009
@@ -540,9 +540,9 @@
          takes about 10 microseconds to write a single logging
          event. When prudent mode is on, it takes approximately 30
          microseconds to output a single logging event. This
-         translates to logging throughput of 100'00 events per second
-         when prudent mode is off and 30'000 events per second in
-         prudent mode.
+         translates to logging throughput of 100'000 events per second
+         when prudent mode is off and approximately 33'000 events per
+         second in prudent mode.
          </p>
        </td>
        

Modified: logback/trunk/logback-site/src/site/pages/news.html
==============================================================================
--- logback/trunk/logback-site/src/site/pages/news.html	(original)
+++ logback/trunk/logback-site/src/site/pages/news.html	Fri Jan  9 18:46:02 2009
@@ -36,7 +36,13 @@
     href="http://jira.qos.ch/browse/LBCLASSIC-89">LBCLASSIC-89</a>
     reported by Alexis Morillo.
     </p>
-    
+
+    <p>Added servleta for viewing internal status messages as an HTML
+    table. Two separate implementations are available; one for <a
+    href="manual/joran.html#viewingStatusMessages">logback-classic</a>
+    and the other for <a
+    href="access.html#viewingStatusMessages">logback-access</a>.</p>
+
     <p>Added the <code>clear()</code> mthod to the
     <code>StatusManager</code> interface. After reconfiguration, it
     may be desirable to clear the status list maintained by a