Name: rlT66838 Date: 07/21/97


The problem is really quite simple: When you do a read() on an SocketInputStream the thread executing the read() blocks if there is no input available.
Normally you should be able to interrupt() the thread, getting an InterruptedIOException and terminating the read(). But in the case of SocketInputStream this does
not work. When exchanging the SocketInputStream with a PipedInputStream in my test program, everything works as expected.
Im my opinion, the implementation of SocketInputStream is broken.


======================================================================