This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [PATCH] for Review: SelectorImpl.wakeup() + Synchronization
- From: Mohan Embar <gnustuff at thisiscool dot com>
- To: Michael Koch <konqueror at gmx dot de>
- Cc: GCJ Patches <java-patches at gcc dot gnu dot org>
- Date: Fri, 19 Dec 2003 10:46:20 -0600
- Subject: Re: [PATCH] for Review: SelectorImpl.wakeup() + Synchronization
- Reply-to: gnustuff at thisiscool dot com
Hi Michael,
>Please read the documentation of AbstractSelector.end() and you will
>see. I think the same applies to AbstractInterruptableChannel.end().
>They throw exceptions if the select (or another blocking IO operation)
>was interrupted somehow.
Nope. AbstractSelector.end() doesn't throw any exceptions. Selector.select()
shouldn't throw exceptions with thread interruption.
Reading the JavaDoc, I think I see how they want us to implement interruption,
but I think they way we've implemented interruptible I/O on POSIX and Win32
precludes us from doing this and forces us to do the inverse: that wakeup()
uses Thread.interrupt() under the covers.
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/