REL1_33/php/ExternalStoreForTesting_8php_source.html

<?php


class ExternalStoreForTesting {


    protected $data = [

        'cluster1' => [

            '200' => 'Hello',

            '300' => [

                'Hello', 'World',

            ],

            // gzip string below generated with gzdeflate( 'AAAABBAAA' )

            '12345' => "sttttr\002\022\000",

        ],

    ];


    public function fetchFromURL( $url ) {

        // Based on ExternalStoreDB

        $path = explode( '/', $url );

        $cluster = $path[2];

        $id = $path[3];

        if ( isset( $path[4] ) ) {

            $itemID = $path[4];

        } else {

            $itemID = false;

        }


        if ( !isset( $this->data[$cluster][$id] ) ) {

            return null;

        }


        if ( $itemID !== false

            && is_array( $this->data[$cluster][$id] )

            && isset( $this->data[$cluster][$id][$itemID] )

        ) {

            return $this->data[$cluster][$id][$itemID];

        }


        return $this->data[$cluster][$id];

    }


}


$path
$path
Definition NoLocalSettings.php:25

ExternalStoreForTesting
Definition ExternalStoreForTesting.php:3

ExternalStoreForTesting\$data
$data
Definition ExternalStoreForTesting.php:5

ExternalStoreForTesting\fetchFromURL
fetchFromURL( $url)
Fetch data from given URL.
Definition ExternalStoreForTesting.php:21

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:37

data
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a and VARBINARY columns should simply be TEXT The only exception is when VARBINARY is used to store true binary data
Definition postgres.txt:37