5981b48bd0
The fundamental insight for this engine is that wiki pages are read far
more often than they are modified. Thus, the generated HTML can be
cached. It follows that the main code path will check that the .html
file exists and simply copy it to stdout in the vast majority of cases.
The .html file generated from each .wiki file is about the same size as
the .wiki file itself, so there will be no particular I/O advantage,
but there is a huge CPU advantage, and a significant memory footprint
advantage, and since I want to run a wiki on a geriatric 20MB 33MHz 386
machine, this is a good thing.
Online demo: http://quickie.sourceforge.net/cgi-bin/quickie
15 lines
827 B
Text
15 lines
827 B
Text
$NetBSD: distinfo,v 1.1.1.1 2006/09/08 04:18:14 samott Exp $
|
|
|
|
SHA1 (quickie-1.1.pdf) = d4bbe6047d7368040463dcb3de56dd9d61cfae64
|
|
RMD160 (quickie-1.1.pdf) = e43504d7a92eadff825d1b54096e216e4aa1c5d3
|
|
Size (quickie-1.1.pdf) = 76778 bytes
|
|
SHA1 (quickie-1.1.tar.gz) = 6725a71fa8661af779f644320f285db4f8efa87f
|
|
RMD160 (quickie-1.1.tar.gz) = 2621cde0cdd3fee816b01b987d355d498855c6a1
|
|
Size (quickie-1.1.tar.gz) = 278045 bytes
|
|
SHA1 (patch-aa) = c0c3b3e852c0931ecbfcdef834e47e767ecd07f3
|
|
SHA1 (patch-ab) = a9179a9acb2716b9469e768332ffe133048daf01
|
|
SHA1 (patch-ac) = 97acc2deb0558bcb5a11425ad0109070eff4bbc2
|
|
SHA1 (patch-ad) = b213685a35821d326172853f2f51be2705c17247
|
|
SHA1 (patch-ae) = 1d1d1443d8de3467a1ac93650b72be5e47488471
|
|
SHA1 (patch-af) = 465f717d4b05dc9b3ece502304a9efe7ca56bfe9
|
|
SHA1 (patch-ag) = 65c261c75bf9d7b57d74626aac4e808812ee884c
|