harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leo Li (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-3037) [classlib][nio]DatagramChannelImpl and SocketChannelImpl lack support for direct byte buffer
Date Wed, 31 Jan 2007 06:30:05 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Leo Li updated HARMONY-3037:

    Attachment: patch-3037_2.zip

Hi, Paulex:
      Thank you for your modification.
      The original patch has been verified.
      And there is one method left in my original one that lacks support for direct buffer
      It is included in the new patch.


> [classlib][nio]DatagramChannelImpl  and SocketChannelImpl lack support for direct byte
> ----------------------------------------------------------------------------------------------
>                 Key: HARMONY-3037
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3037
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Leo Li
>         Assigned To: Paulex Yang
>         Attachments: patch-3037.zip, patch-3037.zip, patch-3037_2.zip
> As spec says, "Given a direct byte buffer, the Java virtual machine will make a best
effort to perform native I/O operations directly upon it. That is, it will attempt to avoid
copying the buffer's content to (or from) an intermediate buffer before (or after) each invocation
of one of the underlying operating system's native I/O operation". However, in Harmony nio,
DatagramChannelImpl and SocketChannelImpl do not differentiate whether the byte buffer is
direct or not.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message