cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-7842) Work out and implement an initialization order for singletons
Date Wed, 02 Mar 2016 19:02:18 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Blake Eggleston resolved CASSANDRA-7842.
----------------------------------------
    Resolution: Later

> Work out and implement an initialization order for singletons
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-7842
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7842
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Blake Eggleston
>            Assignee: Blake Eggleston
>
> Prefer final members passed into their constructor, using volatile members assigned during
startup where there are circular dependencies.
> We should consider splitting some of the singletons into more component specific classes
before this step. There is definitely a case for making that another ticket, but with the
non-singleton dependencies clearly defined at this point, we will have a clear idea of what
can be split up. Doing that would reduce the number of circular dependencies between singletons,
and make this stage a lot easier, with the additional benefit of further modularizing the
code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message