Allow me to follow up on my own post...
I mentioned "Scripted Documents" - this is a name I coined for a way to
package applications: combining scripts and data into a single file, in
such a way that the file can run without unpacking. Because it is based
on a database, such scripted documents can also safely modify themselves
while running.
Quite a mouthful. Scripted Documents were presented at the last Tcl/Tk
conference: http://www.equi4.com/jcw/scripdoc.html (also .ps.gz/.pdf).
The Tcl'ers Wiki is an example of a scripted document, it's a single
file running with TclKit as "runtime".
Various shorter explanations exist, written and different times:
http://www.equi4.com/jcw/wiki.cgi/ScriptedDocument
http://www.equi4.com/metakit/wiki.cgi/18.html
Scripted documents are in production in a range of commercial projects.
So what the previous post described, was how to package tclhttpd in a
single file which runs as is on a range of platforms (with all data,
including logs, residing *inside* that single file). It does not add
functionality to tclhttpd, in fact it does not alter the way tclhttpd
works at all - it merely changes the way software is deployed / used.
-- Jean-Claude
