🚀 go-pugleaf

Kashif Dastgir <kdastgir@yahoo.com> wrote:
> Thanks Torsten,

> Atleast it'll help me to handle the situations where i do have access to I/O
> device of the input class, if not everywhere. However, it seems to be a very
> trivial and common thing, and i'm rather surprised that there doesn't seem
> to be a way out.

> Thanks anyways... and regards!
> Kashif

Here's some info that you might be able to reuse:

http://developer.java.sun.com/developer/technicalArticles/Networking/timeouts/index.html

Pages 79 through 85 of O'Reilly's "Java Threads" book discusses interrupting
blocked I/O threads.  To Summarize, the ability to use Thread.interrupt() on
a thread in an I/O block is JVM-dependent.  It works on Solaris native threads,
but not at all on Windows.

The book says the best way to terminate a blocked thread is to close the
I/O stream/socket/whatever it's blocking on.  That should send an exception
through the I/O class.  The exception you'll get varies with the JVM, it
might be a SocketException, an InterruptedIOException, or something else.

-- 
Joi Ellis (TeamB) 
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Info: http://www.borland.com/newsgroups/guide.html