geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Barrett <>
Subject Re: New client protocol configuration
Date Mon, 02 Oct 2017 19:15:59 GMT
Seriously? Stop with properties already. There are so many better ways to
do configuration. We already have strong APIs for setting up the server as
well as XML which nearly correlates with the API. In fact the XML and API
should be merged together better. Think spring!

For configuration of the new protocol it could just be another "connector"
for clients on the existing "server" element. All configuration related to
it as child elements/attributes of that element. XML has enforceable schema
and type safety and can be parsed directly in to domain objects with JAXB.
You can't get type safety from properties or provide a schema for

Something like this:

<cache xmlns="http:/.../client-10.0" .... xmlns:newclientns="
http://.../client-tng-1.0"  version="10.0">
    <newclientns::connector port="1234">


On Mon, Oct 2, 2017 at 11:56 AM Galen O'Sullivan <>

> Currently, we have a setting for the new client protocol that controls
> whether authentication is required or not. We expect to expand this in the
> future, and also that there may be more configuration options for the
> protocol. We would like to namespace the settings for this protocol but
> don't really have a good name for the protocol.
> We're expecting to do configuration via -- I hear that's
> the right place to put these things. It looks like the setting would take a
> form like ``. "New" client
> protocol is not a good name because it will be outdated before long. It's
> not the only client protocol, so "client-protocol" would be misleading. Any
> other ideas?
> Thanks,
> Galen

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message