whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Baclace (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-303) Refactor ClusterSpec
Date Fri, 01 Feb 2013 00:45:14 GMT

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

Paul Baclace commented on WHIRR-303:
------------------------------------

What is the precise concern here? ClusterSpec should not see a lot of churn, so timely publication
of references is the most likely problem it could see. If so, I think performance would not
suffer much by adding some synchronization which has less code impact for how ClusterSpec
is used. 

Cluster is immutable and that makes it unwieldy to use, but this is worthwhile in this case
since Cluster fields see more churn.

                
> Refactor ClusterSpec
> --------------------
>
>                 Key: WHIRR-303
>                 URL: https://issues.apache.org/jira/browse/WHIRR-303
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>            Reporter: Andrei Savu
>
> Refactor ClusterSpec to be immutable (using the builder pattern). This should make the
object usage more safe.

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