commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CHAIN-101) Change ContextMap from an inheritance based to a delegation based design
Date Fri, 28 Jun 2013 10:46:20 GMT

    [ https://issues.apache.org/jira/browse/CHAIN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695379#comment-13695379
] 

Benedikt Ritter commented on CHAIN-101:
---------------------------------------

Hi,

{quote}
* where higher flexibility is? just to back different Map implementation that could be potentially
not thread safe?
{quote}

I see no point in the provided thread-saftey of ConcurrentHashMap as the functionality we
add is not thread-safe, see my comments on the ML [1] ;)
Maybe we should move this discussion to the ML?

[1] http://markmail.org/message/ngm6gwoz2gx2eaya
                
> Change ContextMap from an inheritance based to a delegation based design
> ------------------------------------------------------------------------
>
>                 Key: CHAIN-101
>                 URL: https://issues.apache.org/jira/browse/CHAIN-101
>             Project: Commons Chain
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Benedikt Ritter
>             Fix For: 2.0
>
>
> Currently ContextMap extends ConcurrentHashMap, but there is nothing we gain from this
design decision. A delegation based implementation that takes a Map as constructor arguments
and delegates calls to the wrapped map yields higher flexibility.

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

Mime
View raw message