harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <j...@apache.org>
Subject [jira] Closed: (HARMONY-635) [classlib][nio]Interruptible channel is not fully implemented
Date Sat, 04 Nov 2006 20:57:17 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-635?page=all ]

Tim Ellison closed HARMONY-635.
-------------------------------


Verified by Paulex.


> [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

        

Mime
View raw message