On 2010/03/23 16:02:13, Paul Lindner wrote:
The map is constructed at startup and then never modified, so this is
a
decent solution, akin to a CopyOnWrite datastructure.
In that case then it doesn't matter that much true. But I am not sure what is the penalty in using ConcurentHashMap. In any case I wouldn't want to use volatile as Henry suggested, since we don't really want to serialize any read requests.
On Tue, Mar 23, 2010 at 8:14 AM, <mailto:[email protected]> wrote:
> On 2010/03/23 13:18:39, Paul Lindner wrote: > >> A different way of dealing with >> https://issues.apache.org/jira/browse/SHINDIG-1283 >> > > The Jira indicates the usage of ConcurrentHashMap which supposedly
not
> required to use synchronize. Wouldn't that be a better way then
using
> synchronized and copy the map for every change? > > > > http://codereview.appspot.com/669043/show >
http://codereview.appspot.com/669043/show
