harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulex Yang (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-635) [classlib][nio]Interruptible channel is not fully implemented
Date Wed, 28 Jun 2006 06:39:30 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-635?page=all ]

Paulex Yang updated HARMONY-635:

    Attachment: 01.nio.diff

As discussion on the mailing list, I proposed to add Thread.setInterruptAction() to VMI, and
implement AbstractInterruptibleChannel and AbstractSelector. Here goes the patch for these
three classes, please try to apply the 01.nio.diff to modules/nio, and 02.luni-kernel.diff
to modules/luni-kernel. 

There are several FIXME left in the codes, and there are no tests included, both because of
current Harmony VM/VMI probably hasn't support this new VMI method, the patch checks the method's
existence at first to be  accommodative, but of course the interruption feature doesn't work
if it doesn't exist.

> [classlib][nio]Interruptible channel is not fully implemented
> -------------------------------------------------------------
>          Key: HARMONY-635
>          URL: http://issues.apache.org/jira/browse/HARMONY-635
>      Project: Harmony
>         Type: Bug

>   Components: Classlib
>     Reporter: Paulex Yang
>  Attachments: 01.nio.diff, 02.luni-kernel.diff
> The java.nio.spi.AbstractInterruptibleChannel and AbstractSelector, according to spec,
need to encapsulate the interrpution machinery in their begin()/end() methods, but currently
Harmony codes don't have this feature yet. As the discussion in mailing list, I proposed a
solution on this by store a command object in java.lang.Thread, so that the Thread.interrupt()
can execute correct action when blocking on I/O or select.
> I will attach patch for nio, luni-kernel and VMI documentation soon.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message