[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile & Sablotron
From: |
Thien-Thi Nguyen |
Subject: |
Re: Guile & Sablotron |
Date: |
Fri, 12 Mar 2004 09:52:42 +0100 |
From: Brian S McQueen <address@hidden>
Date: Tue, 9 Mar 2004 09:32:05 -0800 (PST)
Using a template engine is the way to go for handling the
presentation of data.
i surmise from skimming the axkit homepage that the axkit concept
of "template" is not only the traditional "fill this named space w/
customized bits", but possibly time-varying as well (results are
not fully finalized; tags are kept around; caching is selective).
that's a fine approach to flattening the tree. however, i'm less
than enamored w/ the xml representation, despite its merits.
btw, thanks for your good question on "adding to a list". it
helped spur recent(ish) development of some (www server-utils *)
modules. you can find a work-in-progress (but working nonetheless)
webserver that uses these modules, attached. the first file is the
webserver proper. the second one contains servlets (callbacks for
dynamic content creation). it is left as an exercise for the
reader to write a servlet that uses (database postgres*) modules to
make queries, retrieve scheme objects, and send them over the wire.
axkit-like caching is likewise a SMOP.
thi
_____________________________________________
mgrabmue-webserver.scm
Description: Binary data
mgrabmue-servlets.scm
Description: Binary data