Petter Gustad <firstname.lastname@example.org> wrote:
| "Alex Mizrahi" <email@example.com> writes:
| > UCW keeps lots of data for each user click -- continuations etc. it's
| > obvious you can live without that fancy stuff, but it's not that
| > interesting -- if you want to code in simple CGI manner, it's better to use
| > PHP, i think :)
| Well he said he had his own web-app framework. Allegro Webactions has
| websessions where you can store data associated with the user session.
Yup. And my little web-app framework has a BUILD-CONTINUATION function
that drops one or more <INPUT TYPE=HIDDEN> form data items into the
page currently being output. This allows writing in the flavor of
CPS web app style, albeit without the full generality of the formalism.
It also automatically propagates a small number of "sticky" session
variables, such as debug state and effective-authorization state.
The latter lets "web superusers" execute the app as if they were a
less-privileged user, for development/testing purposes. Note that
because it uses hidden form data, the "state" is in the page being
viewed, *not* the browser instance or the "user login session".
So users can have multiple windows open to the site which are
traversing different paths through the app. [This is "the right
thing" for most apps, though not all.]
Rob Warnock <firstname.lastname@example.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607