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

Hanson Char hanson.char at gmail.com
Wed Mar 17 12:34:39 EDT 2010

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 ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20100317/39001c68/attachment.html>

More information about the Concurrency-interest mailing list