hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19063] - recoverable exceptions when reading are not retried
Date Thu, 17 Apr 2003 12:34:07 GMT
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=19063>.
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=19063

recoverable exceptions when reading are not retried





------- Additional Comments From olegk@apache.org  2003-04-17 12:34 -------
Mike,

- Overall it is a step in the right direction. You know I personally would like
to see retry logic moved from HttpMethodBase to HttpClient, however, for the
time being the patch is a good interim solution 

- isRecoverableAfterReqest is apparently misspelled 

- I think 'isRecoverable*' flag should apply to writing the request as well as
reading the response. There should be a way to disable all sorts of retries. For
instance, the user may want to assign a unique id to each and every request to
the server. Request auto-retry might mess this scheme up. We should also
differentiate between request write recoverable exceptions & failure reading
response exceptions in order to provide the users with a finer control over HTTP
communication. For that end I'd want to see HttpRecoverableException sub-classed
into several specific types of recoverable exceptions

Auto-retries in Sun's implementation of HTTP client was particularly awful. Some
response reads timed out and were subsequently retried. As a result I had
several hits on the server for the same request. That was my primary reason for
dropping Sun's stuff and turning to HttpClient. I strongly believe we should not
fall into the same trap here. 

Oleg

Mime
View raw message