C. R. Oldham said: > OpenACS does this with a scheduled proc that scans the server log for > "Error:". Ouch!
I've been doing a little experimenting. Idea one: do a trace filter and check if any error occured and take action. Doh! errorCode and errorInfo are also set when an error is intercepted by catch. So no good. Attempt two: use an adp error page. Jackpot! errorInfo is not reset between AOLserver catching the error and invoking the errorpage.adp so you can use that. (neither is any other important data about the request) First send the email and then print out a friendly error page. Only downside is that errorpage simply "appends" to whatever has already been sent to screen. (ofcourse it does!) This isn't a problem for me as I write everything needing to go out to a variable anyway, do some mark up magic and then send it out in one go. Not sure how this would work with .tcl pages, but I don't use those anyway. Bas. -- 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.
