This framework is based on log4j (see {@link http://jakarta.apache.org/log4j log4j} for details).
*Design, strategies and part of the methods documentation are developed by log4j team * (Ceki Gülcü as log4j project founder and * {@link http://jakarta.apache.org/log4j/docs/contributors.html contributors}).
* *PHP port, extensions and modifications by VxR. All rights reserved.
* For more information, please see {@link http://www.vxr.it/log4php/}.
This software is published under the terms of the LGPL License * a copy of which has been included with this distribution in the LICENSE file.
* * @package log4php */ /** * @ignore */ if (!defined('LOG4PHP_DIR')) define('LOG4PHP_DIR', dirname(__FILE__)); /** */ require_once(LOG4PHP_DIR . '/LoggerLog.php'); define('LOGGER_MDC_HT_SIZE', 7); /** * This is the global repository of user mappings */ $GLOBALS['log4php.LoggerMDC.ht'] = array(); /** * The LoggerMDC class is similar to the {@link LoggerNDC} class except that it is * based on a map instead of a stack. It provides mapped diagnostic contexts. * * A Mapped Diagnostic Context, or * MDC in short, is an instrument for distinguishing interleaved log * output from different sources. Log output is typically interleaved * when a server handles multiple clients near-simultaneously. * *The MDC is managed on a per thread basis.
*
* @author VxR If the current thread does not have a context map it is
* created as a side effect. Note that you cannot put more than {@link LOGGER_MDC_HT_SIZE} keys. You can use special key identifiers to map values in
* PHP $_SERVER and $_ENV vars. Just put a 'server.' or 'env.'
* followed by the var name you want to refer. This method has no side effects.