diff options
| author | ctrlaltca@gmail.com <> | 2011-12-21 16:20:19 +0000 |
|---|---|---|
| committer | ctrlaltca@gmail.com <> | 2011-12-21 16:20:19 +0000 |
| commit | 73c57b068475257a722286138b55706436625f76 (patch) | |
| tree | 74a0fba931bf5cc547a29da520dc2b15b03539b8 | |
| parent | 32bd39bac3792481079754befe1d6e9d5c6bdd8d (diff) | |
little doc updated related to previous commit
| -rw-r--r-- | HISTORY | 1 | ||||
| -rw-r--r-- | demos/quickstart/protected/pages/Advanced/Logging.page | 7 |
2 files changed, 4 insertions, 4 deletions
@@ -30,6 +30,7 @@ BUG: Issue #181 - Fixed regression introduced by the patch for #181 (ctrlaltca) BUG: Issue #203 - Workaround for ->CallbackClient->click under IE<=8 (ctrlaltca) BUG: Issue #232 - Could not change enable-state of TActiveCheckBox via Ajax callback (Christophe) ENH: Issue #235 - Progressive rendering not possible (Gabor) +BUG: Issue #237 - Log at a long time running process (ctrlaltca) BUG: Issue #240 - TXCache has wrong flush() implementation (ctrlaltca) BUG: Issue #243 - Cross-site scripting issue in TForm (ctrlaltca) BUG: Issue #254 - TDbCache should use hash index for the cache key (ctrlaltca) diff --git a/demos/quickstart/protected/pages/Advanced/Logging.page b/demos/quickstart/protected/pages/Advanced/Logging.page index 357a303a..0b7230b7 100644 --- a/demos/quickstart/protected/pages/Advanced/Logging.page +++ b/demos/quickstart/protected/pages/Advanced/Logging.page @@ -2,7 +2,7 @@ <h1 id="6101">Logging</h1> <p id="780615" class="block-content"> -PRADO provides a highly flexible and extensible logging functionality. Messages logged can be classified according to log levels and message categories. Using level and category filters, the messages can be further routed to different destinations, such as files, emails, browser windows, etc. The following diagram shows the basic architecture of PRADO logging mechanism, +PRADO provides a highly flexible and extensible logging functionality. Messages logged can be classified according to log levels, message categories and originating control. Using level, category, control or timestamp filters, the messages can be further routed to different destinations, such as files, emails, browser windows, etc. The following diagram shows the basic architecture of PRADO logging mechanism, </p> <img src="<%~ logrouter.gif %>" alt="Log router" /> @@ -11,8 +11,8 @@ PRADO provides a highly flexible and extensible logging functionality. Messages The following two methods are provided for logging messages in PRADO, </p> <com:TTextHighlighter CssClass="source block-content" id="code_780201"> -Prado::log($message, $logLevel, $category); -Prado::trace($message, $category); +Prado::log($message, $logLevel, $category, $control); +Prado::trace($message, $category, $control); </com:TTextHighlighter> <p id="780617" class="block-content"> The difference between <tt>Prado::log()</tt> and <tt>Prado::trace()</tt> is that the latter automatically selects the log level according to the application mode. If the application is in <tt>Debug</tt> mode, stack trace information is appended to the messages. <tt>Prado::trace()</tt> is widely used in the core code of the PRADO framework. @@ -58,5 +58,4 @@ Message categories are hierarchical. A category whose name is the prefix of anot <p id="780624" class="block-content"> By convention, the messages logged in the core code of PRADO are categorized according to the namespace of the corresponding classes. For example, messages logged in <tt>TPage</tt> will be of category <tt>System.Web.UI.TPage</tt>. </p> - </com:TContent> |