I'm experimenting with WebWare and have just signed on to this mailing list.
I've done a couple of mid-sized web sites with plain Python CGI and HTTPgen,
and I like the structure that WebKit brings.
However, I'd like to learn more about the strategies that seem to work for real
folks. One of the things I found in my CGI work is that most web transactions
seem to involve three stages:
- Display the page
- Validate the results
- Redirect to next page
I'm pretty clear on how to implement the first two stages with WebKit. I'm not
so clear on common practice for the third. In the past, I've just generated a
simple HTTP redirect using the Refresh: header. This has the downside of
causing another round-trip to the browser, but it does keep the browser's
concept of the current URL in sync with the page contents. It is also possible
to have the "page 1 validator" directly call the "page 2 displayer", but that
leads to confusion, for example, if the users presses refresh. The browser
still thinks it is handling page 1.
Have I made my query
at all clear?
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-discuss
