Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <23153950.1150884989768.JavaMail.jira@brutus>
Date: Wed, 21 Jun 2006 10:16:29 +0000 (GMT+00:00)
From: "Paulex Yang (JIRA)" <jira@apache.org>
To: harmony-commits@incubator.apache.org
Subject: [jira] Created: (HARMONY-635) [classlib][nio]Interruptible channel
 is not fully implemented
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

[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


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