81217f55a0
* Ended the role of $wgLinkCache in link updates. Instead, links (and related entities) are registered in the ParserOutput object during a parse. The LinksUpdate constructor now takes a ParserOutput object as a parameter. $wgLinkCache is still used, but only as a cache of article IDs. * Because the link list is now saved and restored in the parser cache, meta tag keywords now work on parser cache hits. Some refactoring took place in this area. * Rendering of the HTML for category links has moved from Parser to OutputPage. * Did some general pottering around in Article.php, such as allowing an Article object to be created with a specified revision ID, thereby optionally removing the dependence on $wgRequest. Not used at the current time. * A few documentation tweaks.
18 lines
718 B
Text
18 lines
718 B
Text
linkcache.txt
|
|
|
|
The LinkCache class maintains a list of article titles and
|
|
the information about whether or not the article exists in
|
|
the database. This is used to mark up links when displaying
|
|
a page. If the same link appears more than once on any page,
|
|
then it only has to be looked up once. In most cases, link
|
|
lookups are done in batches with the LinkBatch class, or the
|
|
equivalent in Parser::replaceLinkHolders(), so the link
|
|
cache is mostly useful for short snippets of parsed text
|
|
(such as the site notice), and for links in the navigation
|
|
areas of the skin.
|
|
|
|
The link cache was formerly used to track links used in a
|
|
document for the purposes of updating the link tables. This
|
|
application is now deprecated.
|
|
|
|
|