[concurrency-interest] Unmodifiable Navigable{Set,Map} ?

Kevin Bourrillion kevinb at google.com
Wed Mar 17 12:55:13 EDT 2010

If you can make do with the older Sorted{Set,Map} interfaces, there are
array-based immutable implementations in google-collections 1.0.


On Wed, Mar 17, 2010 at 9:34 AM, Hanson Char <hanson.char at gmail.com> wrote:

> Does it make sense to have a "non-concurrent" skip list set/map
> implementation and provide a Collections.unmodifiableNaviable{Set,Map}(...)
> method so clients can choose to operate on an immutable Navigable{Set,Map},
> which is (by definition) both thread-safe and presumably can be a more light
> weight implementation than the existing ConcurrentSkipList{Set,Map} ?  Is
> the current lack of such API's an accident or by intent ?
> Thanks,
> Hanson
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest

Kevin Bourrillion @ Google
internal:  http://goto/javalibraries
external: http://guava-libraries.googlecode.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20100317/a7b0ff80/attachment.html>

More information about the Concurrency-interest mailing list