Timwi wrote:
Oh, sorry, I was in the clouds when I wrote that. Of
course we want to
cache finished pages.
I was just thinking that once we have cachable parse trees, generating
a page from it might not be as intensive and "bottlenecky" as currently.
Here's a thought:
* Have the article as XML (parse tree)
* Have the skin layout as another XML (say,
<topthingy><categories/></topthingy>)
* Have the skin style as CSS
* Profit! :-) (I mean, throw them together by parsing the skim XML tree,
then "collapse" it by replacing <articlebody/> with the XHTML article)
Skin XML could contain things like <sysop> with optional parts for
sysops (delete page etc.) which will be left out for non-sysops.
Also, for specific things like background images, there could be
<skin>backimage</skin>, where the "backimage" function of the skin
class
is called.
Magnus