This is an exception to the general logic that gives direct access to a clone of the underlying ByteBuffer - basically used to enable NIO access
On Wed, Jan 25, 2012 at 5:38 AM, Maurizio Cucchiara (Commented) (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/DIRECTMEMORY-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192857#comment-13192857] > > Maurizio Cucchiara commented on DIRECTMEMORY-43: > ------------------------------------------------ > > Sorry guys, > I would have liked to change the current api layout to <K,V> generics. > Unfortunately there is a logic that I can't understand behind the code. > If you take a look at CacheServiceImpl (http://goo.gl/Ge8X9) you will see > that the method retrieve can return a different kind of object than the > expected one (see line 206). > Generally speaking, I don't like the api methods which force the user to > check what he get, and I would like to get rid of them. > But unfortunately I didn't find a test which documents the need of this > case. > Do we really need it? > > > Cache should allow key objects instead of plain string > > ------------------------------------------------------ > > > > Key: DIRECTMEMORY-43 > > URL: > https://issues.apache.org/jira/browse/DIRECTMEMORY-43 > > Project: Apache DirectMemory > > Issue Type: Improvement > > Reporter: Maurizio Cucchiara > > Assignee: Maurizio Cucchiara > > Attachments: DIRECTMEMORY-43.patch > > > > > > See http://goo.gl/D4SRN > > -- > 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 > > >
