From: Gary B. <ga...@in...> - 2001-11-08 20:13:13
|
On Thu, 8 Nov 2001, Adam Shand wrote: > > > Hmm. You remind me of an optimization I've thought about in the past: > > when a page is saved after editing, convert it to xhtml and store it. > > When pages are served, there's no transformation to do. Almost right. If someone creates or deletes pages which are linked to from a cached page then the cached page will be stale. You'd have to rebuild them then as well. > > When a page is pulled for editing, you have to convert it to wiki > > markup again. The downside, of course, is twice as much code > > (converting between the two formats). Or you could just store the HTML and the wiki-markup in the DB, with the wiki-version being the authoritative version. > the really good thing about this though is that you get the static page > cache. for busy wiki sites having a static page cache becomes a necissity > pretty quickly if you want to survive a slashdotting. :-( If you are running your PhpWiki on your own webserver then you can put a reverse-proxy in front of it. This is what /. does if I remember correctly -- all pages have a five minute expiry time or something. Gary [ ga...@in... ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ] |