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

["Simone Tripodi (Commented) (JIRA)" <ji...@apache.org>]

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

Simone Tripodi commented on DIRECTMEMORY-69:
--------------------------------------------

Salut Benoit,
I am +1 on dropping the behavior of defining the size at-priori, what concerns me is:

 * performances: serializing the Object in a byte array, then put it in the {{ByteBuffer}}, is not something less performant

 * on-heap memory: {{byte[]}} is a data structure that lives anyway in the heap, so it not really good keeping it

If you already have an idea how to improve the current situation, green light from my side! ;)
                
> 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
>
> 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