RE: [HTTPCLIENT] different exception when reading response timed out

[Adrian Sutton <Ad...@Ephox.com>]

Hi Jen,
Hmmm, it seems you can't.  Generally, a HttpRecoverableException (as the
name suggests) means that a retry should work in theory whereas a plain
HttpException means that a retry will most likely fail.  Since HttpClient is
largely intended to remove the need to deal with the Http communication this
distinction is generally enough for people, it seems however it's not enough
for you.

Ideally I suppose the originating exception would be made available through
a getCause() type method to offer more flexibility and this wouldn't be too
difficult to add.  However, HttpClient is desperately trying to get 2.0 beta
1 out the door so I'll have to leave the decision on the exact timing of
this change (or perhaps the HttpClient developers will have an even better
solution).  I would strongly urge you to log a bug in bugzilla
(http://nagoya.apache.org/bugzilla) with this request and include as much
detail about your specific use case as possible.

Regards,

Adrian Sutton, Software Engineer
Ephox Corporation
www.ephox.com 

-----Original Message-----
From: Jen [mailto:xwhu_1999@yahoo.com]
Sent: Friday, 9 May 2003 4:53 AM
To: commons-user@jakarta.apache.org
Subject: [HTTPCLIENT] different exception when reading response timed
out


Hi,

I would like to catch the reading response timed out
exception (normally should be InterruptedIOException)
and deal it specially, but it looks like it is the
HttpRecoverableException, I am assuming it's pretty
general, how can I pick out the exception for timed
out? Thanks

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org