[
https://issues.apache.org/jira/browse/DIRMINA-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-210.
---------------------------------------
Resolution: Won't Fix
Static allocator in ByteBuffer or in IoBuffer have been around for 8 years now.
Nobody complained about it, and I don't see how exposing the allocator can
bring a lot of added value at this point.
For MINA 2, at least, I think it would be insane to change that. For MINA 3,
this can be discussed.
> Investigate removal of static methods in ByteBuffer
> ---------------------------------------------------
>
> Key: DIRMINA-210
> URL: https://issues.apache.org/jira/browse/DIRMINA-210
> Project: MINA
> Issue Type: Improvement
> Components: Core
> Reporter: peter royal
> Assignee: peter royal
> Fix For: 2.0.8
>
>
> The removal of the static methods in ByteBuffer should be investigated.
> Since the ByteBufferAllocator exists, that interface could be used directly.
> For backwards compatibility ( and simple cases ), the static methods could be
> retained and use a supplied instance.
> Potentially, the MINA internals could all access buffers via the allocator,
> leaving only user-code to use the optional static methods (after statically
> supplying the allocator).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
