harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregory Shimansky <gshiman...@gmail.com>
Subject Re: [classlib][luni] Put setInterruptAction() in our j.l.Thread stub?
Date Sat, 09 Sep 2006 23:03:13 GMT
On Friday 08 September 2006 06:03 Jimmy, Jing Lv wrote:
> Geir Magnusson Jr. wrote:
> > This came up in another thread.
> >
> > Currently, java.nio.channels.spi.AbstractInterruptibleChannel depends on
> > there being a setInterruptAction() method on java.lang.Thread.
> >
> > I certainly think that this kind of thing should be documented, so the
> > question - should we add this to our Thread stub class?
>
> Yes, the VMs whose Thread do not know how to interrupt a certain
> understratum blocking I/O(socket read/write, select, or so) is likely to
> use this method. Though DRLVM using SIGUSR2 may not meet this problem(
> does SIGUSR2 work on windows?). I agree this must be documented.

DRLVM doesn't use POSIX signals on windows if you mean if they work in DRLVM.

And if you mean whether they work in the same way as on Linux in regard of 
interrupting blocked IO I don't think so. POSIX signals on windows work in 
their own specific to windows kernel version way which makes them quite 
useless.

+1 of course to document to the above Geir question

-- 
Gregory Shimansky, Intel Middleware Products Division

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org


Mime
View raw message