[jira] [Resolved] (COLLECTIONS-224) [PATCH] Proposal for a new collection type KeyedBuffer

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (COLLECTIONS-224) [PATCH] Proposal for a new collection type KeyedBuffer

Gilles Sadowski (Jira)

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

Thomas Neidhart resolved COLLECTIONS-224.
-----------------------------------------

    Resolution: Won't Fix

The Buffer interface has been removed now, so this is not going to be added anymore.
               

> [PATCH] Proposal for a new collection type KeyedBuffer
> ------------------------------------------------------
>
>                 Key: COLLECTIONS-224
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-224
>             Project: Commons Collections
>          Issue Type: New Feature
>          Components: Buffer
>    Affects Versions: 4.0-beta-1
>            Reporter: Mariusz Krzemien
>         Attachments: KeyedPriorityBuffer-patch.txt
>
>
> Patch contains three new files:
> KeyedPriorityBuffer - class based on PriorityBuffer; with additional support for fast search and remove
> KeyedBuffer - general interface for all buffers containing key-identified elements
> TestKeyedPriorityBuffer - JUnit test cases
> Rationale for introducing new types: I needed a buffer with additional fast search (both get and remove) of elements. I wanted a buffer with search characteristics of a HashMap. But one cannot simply put together a Buffer with a HashMap since the Map needs to have an access to the internal buffer data structures to manage fast remove(key).
> KeyedPriorityBuffer is mixin of a PriorityBuffer with a internal HashMap managing fast search operations.
> KeyedBuffer is a general interface for all such buffers supporting key operations. It extends Map rather than Collection since imho it is more natural.

--
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