Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: "Commons HttpClient Project"
 <commons-httpclient-dev@jakarta.apache.org>
Date: 3 Jul 2004 21:28:42 -0000
Message-ID: <20040703212842.2239.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: commons-httpclient-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 29874]  -
    Auto method retrial broken

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29874>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29874

Auto method retrial broken


------- Additional Comments From olegk@apache.org  2004-07-03 21:28 -------
Mike,
What irks me a little is that socket read timeouts on non-idempotent methods
must be considered fatal, as an attempt to automatically retry an non-idempotent
method may leave the application in an inconsistent state. As HttpClient can't
know whether a method or a sequence of methods are idempotent, it should
probably assume they are not. In this case rethrowing socket timeout as a
recoverable exception sounds wrong, at least from the conceptual standpoint.

I do agree that it might make sense to have connect timeouts treated as
recoverable exceptions. The trouble is that currently only method execution can
be retried automatically, and connection cannot.

Mucking around with MethodRetryHandler was a mistake. Its argument sequence is
ugly, but not uglier than many other things. It makes sense to defer any changes
to it until 4.0

Oleg

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