You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2015/04/07 14:26:12 UTC

[jira] [Resolved] (COLLECTIONS-395) Request for UnBoundedLRUMap implementation with extra get method

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

Thomas Neidhart resolved COLLECTIONS-395.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
                   4.1

Added in r1671832 together with some javadoc fixes.

Thanks for the report!

> Request for UnBoundedLRUMap implementation with extra get method
> ----------------------------------------------------------------
>
>                 Key: COLLECTIONS-395
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-395
>             Project: Commons Collections
>          Issue Type: Wish
>          Components: Map
>    Affects Versions: Nightly Builds
>            Reporter: David Hawthorne
>            Priority: Minor
>             Fix For: 4.1
>
>
> I've created an UnBoundedLRUMap implementation (based off of BoundedLRUMap) using the svn tree at version 3.3, and this has come in so handy that it makes sense to suggest it to the masters in charge of the collections framework.
> One tweak I made to the copy we're using is an extra get method that takes two arguments: key and boolean.  The boolean determines whether or not the MRU item is updated, so we can make requests into the map that do *not* affect order.  This is sometimes necessary in real world environments where you do not want a data structure with LRU-only accesses.
> This implementation would solve the main problem we have with using the jdk's LinkedHashMap LRU implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)