DO NOT REPLY [Bug 19868] - Need the InterruptedIOException when timeout

[bu...@apache.org]

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

Need the InterruptedIOException when timeout





------- Additional Comments From adrian@ephox.com  2003-05-12 22:22 -------
My suggestion for this is to add the ability to get the original exception (if
available) from HttpException, similar to the way that Java 1.4 can wrap
exceptions.  This way we:

a. maintain backwards compatibility
b. make exception catching simple for the non-picky user (like it is currently)
c. allow users with more complex requirements to find out the information they need.

I'll do up an initial patch for this to show the changes to the exception
classes, but we'll have to go through HttpClient and find all the cases where we
create a HttpException because of another exception and pass that through. 
Simple to do with a decent IDE, but my HttpClient code is only in a decent IDE
when I'm at home so that step will have to wait.

My other query is whether or not this should go into 2.0 or leave it for 2.1 -
should it be before or after beta 1?  I think we need to do beta 1 before
looking at anything but total catastrophic failure at the moment.