geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Hanson <mhan...@pivotal.io>
Subject Re: New client protocol configuration
Date Thu, 05 Oct 2017 20:34:32 GMT
One thing also to consider if you modifying the config structure, is an evented config structure,
so that registrants get callbacks if changes are made that are real-time.

Thanks,
Mark
> On Oct 5, 2017, at 12:49 PM, Galen O'Sullivan <gosullivan@pivotal.io> wrote:
> 
> I don't care too much about exactly what the configuration looks like, but
> I want it to be unified, and I want it to be set when the cache starts.
> Checking system properties throughout the codebase whenever we feel like is
> a bit too magic for me.
> 
> In addition, it seems that in order to add a new value to
> DistributionConfig, I have to add it in several places. Config should be in
> one place. Descriptions, values, ranges should be defined in one place and
> Ideally it should be extendable, and it should have some checks to make it
> hard to shoot yourself in the foot.
> 
> For this particular problem, it turns out that we should not make it
> configurable via a property, but should get this information from
> SecurityService. I think that a unified config solution is something we
> should look into for the future, though.
> 
> -Galen


Mime
View raw message