Fabien LE LEZ <firstname.lastname@example.org> wrote:
| Stefan Nobis <email@example.com>:
| >but as a seperate process that communicates via socket
| >with Apache the performance is better).
| Well, well...
| I'll have to learn a new programming paradigm (LISP itself), a new
| HTML-handling paradigm (tree instead of text), and a new
| web-programming paradigm (one big application that handles every
| requests, instead of one little script per request).
You don't need "one big application" per se: One of the useful
features of Common Lisp is that you can compile & load code into
a running program, so you can continue to write separate "web pages"
of code, and have them auto-loaded [and auto-recompiled if they
change!] into the Lisp application server "on demand" [with "JIT"
compilation]. My own LHP (Lisp-Handled Pages) infrastructure does it
that way. Here are a couple of simple examples:
Many other people have done similar things, I sure...
Rob Warnock <firstname.lastname@example.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607