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 16904] - Input Stream closed, Output Stream valid, no detection by socket
Date Sat, 08 Feb 2003 16:47:03 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=16904>.
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=16904

Input Stream closed, Output Stream valid, no detection by socket

ortwin.glueck@nose.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From ortwin.glueck@nose.ch  2003-02-08 16:47 -------
Reporter,

please subscribe to the mailing list:

List-Unsubscribe: <mailto:commons-httpclient-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-httpclient-dev-subscribe@jakarta.apache.org>

Describe your bug there. Provide a test case if possible. Patches are usually
sent to the list in unidiff format, dicussed and approved before checked in.

Feedback to your patch:
It will buffer the whole response which is not good. Imagine a 1GB response. You
would not want this to be buffered, would you.
thread.interrupt() does not kill a thread. It only sets the interrupted flag.
You are not checking for this flag. So the interrupt call will stay unnoticed.

Mime
View raw message