In addition to controls like this, I've also asked for the ability to set logging to errors only. My thinking is that during normal runtime, I really only want to go back and see what went wrong. On the other hand, for debugging a problem, the more options - the better.
I can really see how domain level logging controls would be good, but that too poses some problems. I doubt we'll see logging at this level, but it is a good idea. Robert -----Original Message----- From: William M Conlon [mailto:[EMAIL PROTECTED] Sent: Monday, June 12, 2006 2:24 PM To: Phil Wade Cc: Witango-Talk Subject: Witango-Talk: Logging wish list Hi Phil, I've made some requests about logging facilities, and I recall that John McGowan pointed out the potential security/privacy vulnerability of having postargs present in the log. So anyway, since v6 is in the works, I'm hoping that you'll provide a far more generalized logging model, that gives switches to enable each logging component individually: * appfile execution * search args * post args * appfile action including method calls, but NOT method actions. * object instantiation * method actions * variable results, by scope * sql statements * sql results * html results And of course, I would like the ability to specify both loggingLevel and logDir in app and domain scope in addition to system scope. Bill ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
