[
https://issues.apache.org/jira/browse/DIRECTMEMORY-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215873#comment-13215873
]
Benoit Perroud commented on DIRECTMEMORY-69:
--------------------------------------------
I don't want to drop the actual behavior of allocating buffers of a given size,
this has a lot of sense for most of the actual uses cases.
I'm trying to address the following cases :
- the object to serialize is big (derivate from DIRECTMEMORY-64) ->
serialization need to be buffered to avoid putting all in byte[] first -> the
same problem at deserialization will occur
- the (serialized) size is unknown, for instance reading a file or a socket
(derivated from DIRECTMEMORY-37, but without exposing the internal ByteBuffer)
-> allocation of more data should be transparent for the user.
> 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
