MediaWiki  master
SessionConsistentConnectionManager.php
Go to the documentation of this file.
1 <?php
22 namespace Wikimedia\Rdbms;
23 
45 class SessionConsistentConnectionManager extends ConnectionManager {
46 
50  private $forceWriteConnection = false;
51 
58  public function prepareForUpdates() {
59  $this->forceWriteConnection = true;
60  }
61 
69  public function getReadConnection( array $groups = null ) {
70  if ( $this->forceWriteConnection ) {
71  return parent::getWriteConnection();
72  }
73 
74  return parent::getReadConnection( $groups );
75  }
76 
82  public function getWriteConnection() {
83  $this->prepareForUpdates();
84  return parent::getWriteConnection();
85  }
86 
94  public function getReadConnectionRef( array $groups = null ) {
95  if ( $this->forceWriteConnection ) {
96  return parent::getWriteConnectionRef();
97  }
98 
99  return parent::getReadConnectionRef( $groups );
100  }
101 
107  public function getWriteConnectionRef() {
108  $this->prepareForUpdates();
109  return parent::getWriteConnectionRef();
110  }
111 
112 }
array
The wiki should then use memcached to cache various data To use multiple just add more items to the array To increase the weight of a make its entry a array("192.168.0.1:11211", 2))
Wikimedia\Rdbms\ConnectionManager
Database connection manager.
Definition: ConnectionManager.php:35
Wikimedia\Rdbms\SessionConsistentConnectionManager\prepareForUpdates
prepareForUpdates()
Forces all future calls to getReadConnection() to return a write connection.
Definition: SessionConsistentConnectionManager.php:58
null
this hook is for auditing only or null if authentication failed before getting that far or null if we can t even determine that When $user is not null
Definition: hooks.txt:780
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