You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2012/10/10 13:15:19 UTC

[jira] [Updated] (DIRMINA-210) Investigate removal of static methods in ByteBuffer

     [ https://issues.apache.org/jira/browse/DIRMINA-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRMINA-210:
--------------------------------------

    Fix Version/s:     (was: 2.0.6)
                   2.0.8
    
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira