Perhaps a reference to the "experimental" interface would be helpful. This
"specification" page (
https://cwiki.apache.org/confluence/display/GEODE/Public+Interface+to+Cluster+Configuration+Service)
contains
no links.
*Main question... again, why should the ClusterConfigurationService
interface h
Perhaps org.apache.geode.DataSerializable or
org.apache.geode.internal.DataSerializableFixedID instead of
java.io.Serializable?
Sarge
> On 19 Apr, 2018, at 17:04, Patrick Rhomberg wrote:
>
> E) Every cluster configuration object should be Serializable so that the
> objects may be sent from lo
Hello, all!
I would like to make a few changes to our experimental
ClusterConfigurationService interface, focusing on better ease-of-use and
matching intuition. The majority of these can be achieved very simply by
regenerating our configuration objects from the cache XSD and passing a
JAXB bind