Whoever takes this work on will need to spend time figuring out a way to make it pluggable and support multiple prefixes possibly with pluggable order of preference. For example, we would need to support looking for geode.properties and gemfire.properties or it would break backwards compatibility for users.
On Thu, Sep 14, 2017 at 8:55 AM, Dave Barnes <dbar...@pivotal.io> wrote: > Is there a possibility that the code might find its way into additional > contexts with other names? If so, perhaps we should consider a more generic > identifier, such as PRODUCT_PREFIX. > > On Thu, Sep 14, 2017 at 4:42 AM, Dinesh Akhand <dines...@amdocs.com> > wrote: > > > Hi, > > > > Why we are keeping gemfire in current geode 1.2 , Can we replace this > with > > GEODE > > File : DistributionConfig.java > > > > Current code: > > String GEMFIRE_PREFIX = "gemfire."; > > > > Suggestion to change: > > String GEODE_PREFIX = "geode."; > > > > Why do you think ? > > Can we go ahead and change this ? > > It will impact lots of files & all configuration will be now using with > > geode. > > > > Thanks, > > Dinesh Akhand > > This message and the information contained herein is proprietary and > > confidential and subject to the Amdocs policy statement, > > > > you may review at https://www.amdocs.com/about/email-disclaimer < > > https://www.amdocs.com/about/email-disclaimer> > > >
