Mailing-List: contact directmemory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: directmemory-dev@incubator.apache.org
Date: Fri, 24 Feb 2012 09:06:49 +0000 (UTC)
From: "Olivier Lamy (Updated) (JIRA)" <jira@apache.org>
To: directmemory-dev@incubator.apache.org
Message-ID: 
 <1686759951.14580.1330074409711.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1892555211.31300.1322757400151.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DIRECTMEMORY-37) Update the MemoryManager API so
 it can be used in conjunction with NIO to provide efficient buffer
 management
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Olivier Lamy updated DIRECTMEMORY-37:
-------------------------------------

    Fix Version/s: 0.6.0
    
> Update the MemoryManager API so it can be used in conjunction with NIO to provide efficient buffer management
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRECTMEMORY-37
>                 URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-37
>             Project: Apache DirectMemory
>          Issue Type: New Feature
>            Reporter: Hiram Chirino
>             Fix For: 0.6.0
>
>
> If MemoryManager implemented something like a ByteBuffer allocate(int size) then I could be used to directly transfer data to/from Files and Sockets without having to first copy them to a byte[].
> I'm not talking about using the ByteBuffer.allocate call. I'm talking about adding a method to MemoryManager:
> ByteBuffer bb = MemoryManager.allocate(1024*1024);
> So that I can directly modify the ByteBuffer using Channels to avoid a memory copy.. Compare this to using the MemoryManager store, update, and retrieve calls. They all force you to work with byte[]s so you end up doing a memory copies into and out of direct memory.
> This was originally reported at: https://github.com/raffaeleguidi/DirectMemory/issues/49#issuecomment-2661141

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira