On 11/25/05, S. Woodside <sbwoodside(a)yahoo.com> wrote:
ARTICLE
- for storing the content
The unit of content is a 3-tuple: {wikitext, red coloured links,
templates}
- each time I am edited:
--- change my content
--- if I'm a new/moved article, change colour of links in articles
that reference me
--- if I'm a template, change each article that uses me
- goal:
--- when I'm edited, propagate those changes as *efficiently* as
possible to my fellow articles
--- insist that when I'm changed, directly or indirectly, I am only
read *once* by the Content cache
--- insist that I'm only changed by the authentication server
And so you perform a linear scan of all articles redlinks to find the
ones you must remove and a reparse of all articles to find the
redlinks you must add every time there is a move or delete?
Moves only decrease redlinks, but deletes must be handled as well.
We have enough people dreaming up ideas, myself included.
Show us the code, and the benchmarks.