DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19868>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19868 Exception handling in HttpClient requires redesign ------- Additional Comments From [EMAIL PROTECTED] 2003-07-14 23:00 ------- Oleg, Agreed there are definitely times where nested exceptions are better. I guess my main question has come down to: how is HttpTransportException() different and better than IOException? My understanding of IOException is that it's thrown when communication goes wrong, which is the same as my understanding of HttpTransportException. For the record I definitely agree we should nest exceptions like JSSE and crypto exceptions as well as other exceptions that are very much internal to how HttpClient works. I'm just not sure that TransportException either shields the user from the internals of HttpClient or provides additional information that may be useful. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
