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-safety
Date Mon, 25 Oct 2010 14:11:22 GMT

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

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

Any hint on what could be the best practice to make that classes as thread safety?
Configurations properties are mutable, so let's keep out the {{final}} option; we can opt
for making:

 * {{volatile}} Configuration fields;
 * {{synchronized}} (g|s)etters;

I'm asking because you'll know more than me, so let's discuss about it. I'm more for making
{{volatile}} the fields.
Thoughts?

> Configuration classes must be thread-safety
> -------------------------------------------
>
>                 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