[
https://issues.apache.org/jira/browse/DIRMINA-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621928#action_12621928
]
Julien Vermillard commented on DIRMINA-489:
-------------------------------------------
today I was digging in old asyncweb codebase because at the time it was using
some streams & byte arrays as HttpMessage contents and not IoBuffer. Here a
link to the implementation :
https://svn.safehaus.org/repos/asyncweb/branches/asyncweb-codefreeze-02132006/src/org/safehaus/asyncweb/io/
(mainly Bytes.java and BytesOutputStream.java). Perhaps it can give some
inspiration :)
> Composite IoBuffer
> ------------------
>
> Key: DIRMINA-489
> URL: https://issues.apache.org/jira/browse/DIRMINA-489
> Project: MINA
> Issue Type: New Feature
> Components: Core
> Reporter: David M. Lloyd
> Assignee: Mark Webb
> Fix For: 2.0.0-M4
>
> Attachments: mina-composite-20080515.patch.gz,
> mina-composite-20080517.patch, mina-composite-20080521-2.patch,
> mina-composite-20080521.patch, mina-composite-20080723-1.patch,
> mina-composite-20080723-2.patch
>
>
> Provide a way to create a large IoBuffer from several smaller IoBuffers,
> without copying the underlying data.
> It would probably be acceptable to constrain the composite buffer in various
> ways, for example by disallowing autoexpanding or otherwise changing the
> capacity, the implementation could be greatly simplified.
> The goal is to be able to process large messages with a minimum of copying.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
