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-15 14:42 ------- OK. Here's what I got. I played around with several approaches and realized that wrapping all IOExceptions into HttpTransportExceptions was not simply feasible, primarily because InputStream / OutputStream derived classes cannot throw non-IOExceptions. I found no way to work that problem around in an acceptable manner The patch basically implements the first scenario of my original proposal and goes along the line suggested by Adrian: * IOException represents transport exceptions * HttpException represents protocol exceptions Here's the list of important points * TransportException no more * HttpException is no longer derived from IOException (which is good) * URIException is no longer derived from IOException (which is good) * I had to deprecate HttpConnectionManager#getConnection(HostConfiguration, long) because of wrong exception type it throws. * In ChunkedInputStream I had to implement a pretty ugly hack to work around exception type mismatch * HttpConnection can now throw IOTimeoutException Let me know what you think Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
