From: Colin M. <co...@ch...> - 2004-10-07 10:47:50
|
On Thu, 2004-10-07 at 19:14, Nicolas Boretos wrote: > As much as I > understand, "tclhttpd" is my "single user", and that > read/writes are sequential/serialized, the equivalent of opening a > console and playing with the mk db... That's a good way to look at it. > We are running single threaded tclkit, with the stripped down > tclhttpdmin.kit for the web-server, on a debian3 box Debian and tclhttpd? You are clearly a man of discretion and good taste. :) > A few key points about the app. > 1. A .tclaccess file permits access to the db Wrong place. Should be a .tml file (just dir/.tml is sourced in.) > 2. From then on, ncgi package is used for user_id and all form variables > 3. The whole app uses self-posting .tml pages, with Doc_Redirects to the > next page... I like this approach, I like .tml pages. Handling state through Redirects is a pain though. Perhaps we should come up with a nicer abstraction to cover the messy details of building systems of DFSAs to represent interactions via templates. One facility you should become familiar with is [Httpd_Suspend] and [Httpd_Resume], which allows you to leave the connection open (for some period) while processing other incoming connections. It might be useful in this application. -- Colin McCormack <co...@ch...> |