Go to the documentation of this file.
54 if ( !isset( self::$instances[
$domain] ) ) {
56 self::$instances[
$domain]->initFromGlobals();
59 return self::$instances[
$domain];
66 self::$instances = [];
84 protected function register(
array $configs ) {
85 foreach ( $configs
as $config ) {
87 if ( !isset( $config[
'name'] ) ) {
88 throw new Exception(
"Cannot register a lock manager with no name." );
90 $name = $config[
'name'];
91 if ( !isset( $config[
'class'] ) ) {
92 throw new Exception(
"Cannot register lock manager `{$name}` with no class." );
94 $class = $config[
'class'];
95 unset( $config[
'class'] );
96 $this->managers[
$name] = [
112 if ( !isset( $this->managers[
$name] ) ) {
113 throw new Exception(
"No lock manager defined with the name `$name`." );
116 if ( !isset( $this->managers[
$name][
'instance'] ) ) {
117 $class = $this->managers[
$name][
'class'];
118 $config = $this->managers[
$name][
'config'];
119 if ( $class ===
'DBLockManager' ) {
120 $lbFactory = MediaWikiServices::getInstance()->getDBLoadBalancerFactory();
121 $lb = $lbFactory->newMainLB( $config[
'domain'] );
122 $dbw = $lb->getLazyConnectionRef(
DB_MASTER, [], $config[
'domain'] );
124 $config[
'dbServers'][
'localDBMaster'] = $dbw;
127 $config[
'logger'] = LoggerFactory::getInstance(
'LockManager' );
129 $this->managers[
$name][
'instance'] =
new $class( $config );
132 return $this->managers[
$name][
'instance'];
143 if ( !isset( $this->managers[
$name] ) ) {
144 throw new Exception(
"No lock manager defined with the name `$name`." );
146 $class = $this->managers[
$name][
'class'];
148 return [
'class' => $class ] + $this->managers[
$name][
'config'];
158 return isset( $this->managers[
'default'] )
159 ? $this->
get(
'default' )
172 return isset( $this->managers[
'default'] )
173 ? $this->
get(
'default' )
174 : $this->
get(
'fsLockManager' );
processing should stop and the error should be shown to the user * false
static destroySingletons()
Destroy the singleton instances.
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to use
static singleton( $domain=false)
Allows to change the fields on the form that will be generated $name
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
static LockManagerGroup[] $instances
(domain => LockManagerGroup)
getAny()
Get the default lock manager configured for the site or at least some other effective configured lock...
Simple version of LockManager that does nothing.
$wgLockManagers
Array of configuration arrays for each lock manager.
Class to handle file lock manager registration.
when a variable name is used in a it is silently declared as a new masking the global
wfWikiID()
Get an ASCII string identifying this wiki This is used as a prefix in memcached keys.
initFromGlobals()
Register lock managers from the global variables.
config( $name)
Get the config array for a lock manager object with a given name.
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
MediaWiki Logger LoggerFactory implements a PSR[0] compatible message logging system Named Psr Log LoggerInterface instances can be obtained from the MediaWiki Logger LoggerFactory::getInstance() static method. MediaWiki\Logger\LoggerFactory expects a class implementing the MediaWiki\Logger\Spi interface to act as a factory for new Psr\Log\LoggerInterface instances. The "Spi" in MediaWiki\Logger\Spi stands for "service provider interface". An SPI is an API intended to be implemented or extended by a third party. This software design pattern is intended to enable framework extension and replaceable components. It is specifically used in the MediaWiki\Logger\LoggerFactory service to allow alternate PSR-3 logging implementations to be easily integrated with MediaWiki. The service provider interface allows the backend logging library to be implemented in multiple ways. The $wgMWLoggerDefaultSpi global provides the classname of the default MediaWiki\Logger\Spi implementation to be loaded at runtime. This can either be the name of a class implementing the MediaWiki\Logger\Spi with a zero argument const ructor or a callable that will return an MediaWiki\Logger\Spi instance. Alternately the MediaWiki\Logger\LoggerFactory MediaWiki Logger LoggerFactory
getDefault()
Get the default lock manager configured for the site.
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency MediaWikiServices
the array() calling protocol came about after MediaWiki 1.4rc1.
static getLocalServerInstance( $fallback=CACHE_NONE)
Factory function for CACHE_ACCEL (referenced from DefaultSettings.php)
array $managers
Array of (name => ('class' => ..., 'config' => ..., 'instance' => ...))