You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2014/08/27 19:49:58 UTC

[jira] [Created] (CASSANDRA-7842) Work out and implement an initialization order for singletons

Blake Eggleston created CASSANDRA-7842:
------------------------------------------

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


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.2#6252)