I'm doing a build-all right now so that I can take a look at mailreader... I admit I haven't really looked at mailreader before much, so I'm not familiar with how much logging is in there (maybe a good thing to not be going in with any preconconceived notions). I'm a fan of logging, but I agree that too much can get in the way (not to mention potentially hurt performance). I'm hoping I can offer some suggestions on what messages are superfluous and which should probably stay, at least as a more concrete starting point for discussion.

(Wow, you guys weren't kidding, the build is taking FOREVER! I've done it before a few months back, but I don't remember it taking this long... I guess all the restructuring and such has an impact).

Frank

Don Brown wrote:
Ted Husted wrote:

This thread started with a comment that we should leave the debug
logging in MailReader to appeal to the "lowest common denominator".
But, I think this thread shows that extensive logging appeals to the
other end of the spectrum :)


I'd like to see the logging taken down a notch, but perhaps not completely out. IMO, Mailreader is there to demonstrate Struts best practices and the logging statements everywhere make one wonder :) Besides, it gives a false impression Actions need to be long and detailed. I'd rather see if we can get those Actions down under 10 lines each. Leave "*Action was called"-type statements to the framework.

Don


-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to