MediaWiki  1.32.5
load.php
Go to the documentation of this file.
1 <?php
25 use MediaWiki\Logger\LoggerFactory;
26 use MediaWiki\MediaWikiServices;
27 
28 // This endpoint is supposed to be independent of request cookies and other
29 // details of the session. Enforce this constraint with respect to session use.
30 define( 'MW_NO_SESSION', 1 );
31 
32 require __DIR__ . '/includes/WebStart.php';
33 
34 // URL safety checks
35 if ( !$wgRequest->checkUrlExtension() ) {
36  return;
37 }
38 
39 // Disable ChronologyProtector so that we don't wait for unrelated MediaWiki
40 // writes when getting database connections for ResourceLoader. (T192611)
41 MediaWikiServices::getInstance()->getDBLoadBalancerFactory()->disableChronologyProtection();
42 
43 // Set up ResourceLoader
44 $resourceLoader = new ResourceLoader(
45  ConfigFactory::getDefaultInstance()->makeConfig( 'main' ),
46  LoggerFactory::getInstance( 'resourceloader' )
47 );
48 $context = new ResourceLoaderContext( $resourceLoader, $wgRequest );
49 
50 // Respond to ResourceLoader request
51 $resourceLoader->respond( $context );
52 
53 Profiler::instance()->setTemplated( true );
54 
55 $mediawiki = new MediaWiki();
56 $mediawiki->doPostOutputShutdown( 'fast' );
ResourceLoaderContext
Object passed around to modules which contains information about the state of a specific loader reque...
Definition: ResourceLoaderContext.php:32
Profiler\instance
static instance()
Singleton.
Definition: Profiler.php:62
$resourceLoader
$resourceLoader
Definition: load.php:44
php
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
Definition: injection.txt:35
$mediawiki
$mediawiki
Definition: load.php:55
MediaWiki
This document describes the state of Postgres support in MediaWiki
Definition: postgres.txt:4
ConfigFactory\getDefaultInstance
static getDefaultInstance()
Definition: ConfigFactory.php:51
use
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
Definition: MIT-LICENSE.txt:10
$context
$context
Definition: load.php:48
LoggerFactory
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
Definition: logger.txt:5
$wgRequest
if(! $wgDBerrorLogTZ) $wgRequest
Definition: Setup.php:747
MediaWikiServices
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
Definition: injection.txt:23