[ http://issues.apache.org/jira/browse/JAMES-709?page=comments#action_12454451 ] Robert Burrell Donkin commented on JAMES-709: ---------------------------------------------
it looks ok but it's hard for me to test this code: my local version has drifted away from James. I definitely agree that the ideal would be for each issue to be logged once and only once. For this to work, it is crucial that in every case that an exception is caught and a wrapping exception is thrown. My IMAP is currently slow but stable. Logging makes a huge difference to the usability of IMAP ATM. Being experimental, it's important that the logs can be used effectively without having to dive into the source. If you need help going through the code, let me know. > [PATCH] Log IO issues to help diagnosis > --------------------------------------- > > Key: JAMES-709 > URL: http://issues.apache.org/jira/browse/JAMES-709 > Project: James > Issue Type: Improvement > Components: IMAPServer > Affects Versions: Trunk > Reporter: Robert Burrell Donkin > Assigned To: Joachim Draeger > Attachments: james-imap-io-diagnostics.patch > > > Log IO issues to help diagnostics -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
