You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directmemory.apache.org by "Christoph Engelbert (JIRA)" <ji...@apache.org> on 2012/10/31 21:47:12 UTC

[jira] [Commented] (DIRECTMEMORY-69) Expose InputStream and OutputStream Interfaces instead of internal Pointer.directBuffer

    [ https://issues.apache.org/jira/browse/DIRECTMEMORY-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488213#comment-13488213 ] 

Christoph Engelbert commented on DIRECTMEMORY-69:
-------------------------------------------------

Sorry haven't seen this earlier. I'd added a Buffer interface which encapsulates all kinds of backend technologies (like sun.misc.Unsafe, ByteBuffer (on- / offheap), files, ...). The new interface is called MemoryBuffer ( http://svn.apache.org/repos/asf/directmemory/trunk/directmemory-cache/src/main/java/org/apache/directmemory/memory/buffer/MemoryBuffer.java ). Is this what you need or do you want some more stuff handled?
                
> Expose InputStream and OutputStream Interfaces instead of internal Pointer.directBuffer
> ---------------------------------------------------------------------------------------
>
>                 Key: DIRECTMEMORY-69
>                 URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-69
>             Project: Apache DirectMemory
>          Issue Type: Improvement
>            Reporter: Benoit Perroud
>            Assignee: Benoit Perroud
>         Attachments: DIRECTMEMORY-69-in-and-out-streams.patch
>
>
> Providing an InputStream and OutputStream interface would be a clean way to reconciliate both DIRECTMEMORY-37 and DIRECTMEMORY-64 ?
> Allocation of more space would be done in the backend, no need to predefine a size.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira