MediaWiki REL1_28
Go to the documentation of this file.
31interface IExpiringStore {
32 // Constants for TTL values, in seconds
33 const TTL_MINUTE = 60;
34 const TTL_HOUR = 3600;
35 const TTL_DAY = 86400; // 24 * 3600
36 const TTL_WEEK = 604800; // 7 * 24 * 3600
37 const TTL_MONTH = 2592000; // 30 * 24 * 3600
38 const TTL_YEAR = 31536000; // 365 * 24 * 3600
40 // Shorthand process cache TTLs (useful for web requests and CLI mode)
41 const TTL_PROC_SHORT = 3; // reasonably strict cache time that last the life of quick requests
42 const TTL_PROC_LONG = 30; // loose cache time that can survive slow web requests
44 const TTL_INDEFINITE = 0;
46 // Attribute and QoS constants; higher QOS values with the same prefix rank higher...
47 // Medium attributes constants related to emulation or media type
48 const ATTR_EMULATION = 1;
50 // Medium attributes constants related to replica consistency
51 const ATTR_SYNCWRITES = 2; // SYNC_WRITES flag support
52 const QOS_SYNCWRITES_NONE = 1; // replication only supports eventual consistency or less
53 const QOS_SYNCWRITES_BE = 2; // best effort synchronous with limited retries
54 const QOS_SYNCWRITES_QC = 3; // write quorum applied directly to state machines where R+W > N
55 const QOS_SYNCWRITES_SS = 4; // strict-serializable, nodes refuse reads if possible stale
56 // Generic "unknown" value that is useful for comparisons (e.g. always good enough)
57 const QOS_UNKNOWN = INF;
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
Generic base class for storage interfaces.