[
https://issues.apache.org/jira/browse/GEODE-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779777#comment-16779777
]
ASF subversion and git services commented on GEODE-6380:
--------------------------------------------------------
Commit c12e5f3f32f8ee5b2d4bae2c457fbf3509df53a2 in geode's branch
refs/heads/develop from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c12e5f3 ]
GEODE-6380: Getting rid of nextOrindal pattern
We had some mutable statics that used a static nextOrdinal++ pattern.
This code worked, but it wasn't really necessary so removing the pattern
in favor of completely immutable static state.
> Remove all mutable static state from Geode
> ------------------------------------------
>
> Key: GEODE-6380
> URL: https://issues.apache.org/jira/browse/GEODE-6380
> Project: Geode
> Issue Type: Bug
> Components: core
> Reporter: Dan Smith
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Related to GEODE-395 and GEODE-3583 - we would like to eliminate the use of
> mutable static state within Geode. This sort of state
> - prevents us from running multiple caches in the same JVM
> - provides opportunities for bugs related to not cleaning up static state
> - Makes it harder to understand and test components that may have hidden
> dependencies through static state.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
