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 38231] - request doesn't timeout when response is slow
Date Fri, 13 Jan 2006 08:13:19 GMT
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=38231>.
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=38231





------- Additional Comments From odi@odi.ch  2006-01-13 09:13 -------
Mike,

For 3.0 you are out of luck as there is no other option than spawning a new
thread per call. For 4.0 it may look better since we are going to use
non-blocking NIO.

I fully understand the need for timeouts in blocking call. One could call it a
major ommission in the API actually.

> Do you have the capability to set the socket timeout prior to each packet
recieved?

Not really. We use the java.net.Socket API, which does not allow accessing
individual packets. So data in the buffer may be from one or more packets. But
you can change the SO_TIMEOUT value while the socket is open! See
HttpConnection.setSocketTimeout

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message