[
http://issues.apache.org/jira/browse/DIRMINA-165?page=comments#action_12370050
]
Trustin Lee commented on DIRMINA-165:
-------------------------------------
I realized the solution I mentioned above was not really easy to implement
after wasting an hour. :(
Federico's solution doesn't resolve the problem in the following scenario:
buf = ...;
dupBuf = buf.duplicate();
buf.release();
newBuf = ByteBuffer.allocate( ... ); // newBuf can be the same instance
with buf
dupBuf.release(); // This will lead us to a big mess.
> Easy and performant copy of the ByteBuffer
> ------------------------------------------
>
> Key: DIRMINA-165
> URL: http://issues.apache.org/jira/browse/DIRMINA-165
> Project: Directory MINA
> Type: Improvement
> Versions: 0.9, 0.8.2, 0.8.1, 0.8
> Reporter: Federico Bonelli
> Priority: Minor
> Fix For: 0.9.3
> Attachments: ByteBuffer.java, HubServer_broadCastTCPmessages.zip
>
> Until now if you wish to broadcast a message you must create by your own the
> bytebuffer copies, it would be better to provide a ByteBuffer.asReadOnly()
> method that create a copy that share the data with the original ByteBuffer
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
