You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Paulex Yang (JIRA)" <ji...@apache.org> on 2006/07/24 03:59:15 UTC
[jira] Commented: (HARMONY-635) [classlib][nio]Interruptible
channel is not fully implemented
[ http://issues.apache.org/jira/browse/HARMONY-635?page=comments#action_12422952 ]
Paulex Yang commented on HARMONY-635:
-------------------------------------
Tim, sorry for late response, looks good, thank you.
> [classlib][nio]Interruptible channel is not fully implemented
> -------------------------------------------------------------
>
> Key: HARMONY-635
> URL: http://issues.apache.org/jira/browse/HARMONY-635
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Paulex Yang
> Assigned To: Tim Ellison
> 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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira