commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (POOL-174) Configuration classes must be thread-safe
Date Mon, 25 Oct 2010 18:06:21 GMT

    [ https://issues.apache.org/jira/browse/POOL-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924656#action_12924656
] 

Simone Tripodi commented on POOL-174:
-------------------------------------

Since the same configuration is shared between the related factory/pool (the POOL-173 implements
James' hint at 95%), and both require to be thread-safe, it should be useful making the configuration
classes thread-safe to centralize the synchronized accesses instead of repeating the same
pattern on wrappers.
WDYT?

> Configuration classes must be thread-safe
> -----------------------------------------
>
>                 Key: POOL-174
>                 URL: https://issues.apache.org/jira/browse/POOL-174
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Simone Tripodi
>            Assignee: Simone Tripodi
>             Fix For: 2.0
>
>
> New Configuration classes added with POOL-173 have to be made thread-safety

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message