Where it gets all annoying, though, is preAction and postAction, which are like an anemic form of the writeHTML, writeHead, writeTitle, writeStyleSheet etc. setup that Page has for normal requests. Or, where you don't want to write anything, but way to treat the action as an action (i.e., something that does something, not something that merely changes the display) -- there again preAction and postAction get in the way.There's a diagram in the docs for our FormKit that may help clarify the situation:
http://dalchemy.com/opensource/formkit/architecture.html
About half way down.
For form processing, we changed pre-action and post-action to merge the lifecycle more closely back into the normal respond; basically, we call writeHTML from post-action, which effectively inserts actions in *before* the output, rather than doing "some" of the output in pre/post.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
