61 if ( $domain instanceof
self ) {
65 $parts = array_map( [ __CLASS__,
'decode' ], explode(
'-', $domain ) );
70 if ( count( $parts ) == 1 ) {
72 } elseif ( count( $parts ) == 2 ) {
74 } elseif ( count( $parts ) == 3 ) {
91 return new self( null, null,
'' );
101 $this->
database === $other->database &&
102 $this->schema === $other->schema &&
103 $this->prefix === $other->prefix
107 return ( $this->
getId() === $other );
135 if ( $this->equivalentString === null ) {
147 if ( $this->schema !== null ) {
150 if ( $this->prefix !=
'' ) {
154 return implode(
'-', array_map( [ __CLASS__,
'encode' ], $parts ) );
157 private static function encode( $decoded ) {
160 $length = strlen( $decoded );
161 for ( $i = 0; $i < $length; ++$i ) {
162 $char = $decoded[$i];
163 if ( $char ===
'-' ) {
165 } elseif ( $char ===
'?' ) {
175 private static function decode( $encoded ) {
178 $length = strlen( $encoded );
179 for ( $i = 0; $i < $length; ++$i ) {
180 $char = $encoded[$i];
181 if ( $char ===
'?' ) {
182 $nextChar = isset( $encoded[$i + 1] ) ? $encoded[$i + 1] : null;
183 if ( $nextChar ===
'h' ) {
186 } elseif ( $nextChar ===
'?' ) {
204 return $this->
getId();
deferred txt A few of the database updates required by various functions here can be deferred until after the result page is displayed to the user For updating the view updating the linked to tables after a etc PHP does not yet have any way to tell the server to actually return and disconnect while still running these but it might have such a feature in the future We handle these by creating a deferred update object and putting those objects on a global list
string $equivalentString
Cache of convertToString()
__construct($database, $schema, $prefix)
Class to handle database/prefix specification for IDatabase domains.
design txt This is a brief overview of the new design More thorough and up to date information is available on the documentation wiki at etc Handles the details of getting and saving to the user table of the database
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 newFromId($domain)