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
14 lines
611 B
Text
14 lines
611 B
Text
===========================================================================
|
|
$NetBSD: MESSAGE,v 1.1.1.1 2006/09/08 04:18:14 samott Exp $
|
|
|
|
Quickie has been installed. Quickie's files are stored in
|
|
standard system locations, rather than all under the web
|
|
root. In order for Quickie to be accessible, a copy - or
|
|
symlink if your web server supports it - of the CGI binary
|
|
must be made to the cgi-bin directory of your web server:
|
|
|
|
cp -p ${PREFIX}/bin/quickie /path/to/cgi-bin
|
|
|
|
This file should be owned by www:www, and be executable.
|
|
|
|
===========================================================================
|