Hi all I'm trying to understand the lifecycle of a TCL interpreter in AOLserver, in order to be aware of how variables persist and so avoid issues that might cause - as well as potentially take advantage of any useful features.
http://panoptic.com/wiki/aolserver/119 is a bit lacking on this front, but I've found http://philip.greenspun.com/doc/programming-with-aolserver and http://www.aolserver.com/docs/devel/tcl/tcl-general.html However, these appear to be written a while back, so I'd like to ask how accurately they apply to AOLserver 4? Certainly trial-and-error does seem to indicate that variables set within a template do not persist across requests (ignoring nsv_*), and that namespace-specific variables set during initialisation are visible during template execution - tying in with what's suggested about cloning a post-startup interpreter's state. The exception being global variables which appear to be completely cleared down before each template is executed - even if they were set during server startup. Two other (unrelated) questions: Firstly, it appears that when parsing ADP, if a TCL error is encountered during a <%...%> block, AOLserver simply logs the error, that block is replaced with an empty string in the output (or the contents of 'errorpage' if set), and execution of the rest of the ADP continues. My question is whether there's a way to configure AOLserver such that execution terminates as soon as a TCL error is hit? If it's relevant, I'm calling adp_parse_file inside catch (which currently fails to spot the errors) - though the behaviour seems to be the same with the file mapped to the ADP parsing in the default manner. Secondly, does AOLserver have a built-in method to terminate template/request execution after a fixed amount of time? TIA -- Stuart Children -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
