Hi,
Is there a reason why these two calls to log-message in server.lisp are not wrapped in (when *log-lisp-warnings-p*) and (when *log-lisp-errors-p*) like they are in process-request?
(defun process-connection (server handle) "This...occurs." (handler-bind ((error ;; abort if there's an error which isn't caught inside (lambda (cond) (log-message *lisp-errors-log-level* "Error while processing connection: ~A" cond) (return-from process-connection))) (warning ;; log all warnings which aren't caught inside (lambda (cond) (log-message *lisp-warnings-log-level* "Warning while processing connection: ~A" cond))))
Hunchentoot is wonderful software, BTW. I use it here: http://syseng.nist.gov/se-interop and here http://syseng.nist.gov/moss
On Thu, 15 Mar 2007 19:41:07 -0400, Peter Denno peter.denno@nist.gov wrote:
Is there a reason why these two calls to log-message in server.lisp are not wrapped in (when *log-lisp-warnings-p*) and (when *log-lisp-errors-p*) like they are in process-request?
Yes, these variables are supposed to control whether errors or warnings which happen within /handlers/ are logged. Hunchentoot unconditionally logs unexpected events that don't happen in "user code."
Hunchentoot is wonderful software, BTW. I use it here: http://syseng.nist.gov/se-interop and here http://syseng.nist.gov/moss
Ah, nice!
Cheers, Edi.
-
Edi Weitz -
Peter Denno