You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directmemory.apache.org by "Benoit Perroud (Updated) (JIRA)" <ji...@apache.org> on 2012/03/04 11:02:54 UTC

[jira] [Updated] (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:all-tabpanel ]

Benoit Perroud updated DIRECTMEMORY-69:
---------------------------------------

    Attachment: DIRECTMEMORY-69-in-and-out-streams.patch

First throw of input and output streams. The idea is to provide a wrapper class {{{OffHeapStream}}} that reference both {{{OffHeapInputStream}}} and {{{OffHeapOutputStream}}} to be able to write off-heap, and then read as many times as wanted.

Feedback welcome !
                
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira