[
https://issues.apache.org/jira/browse/ZOOKEEPER-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061866#comment-17061866
]
Enrico Olivelli commented on ZOOKEEPER-3762:
--------------------------------------------
At first glance I am not sure this is a good idea, expectially because:
- server and client are very much decoupled
- you can update the server (version or simply avaiable features) and the
client should be notified of a new configuration ?
- you can have mixed versions in a cluster (expectially during rolling
upgrades), so the client cannot assume that every server has the same
capabilites
- many zk clusters are configured in a way that every server has the same dns
name for clients, but servers may differ and this will cause much confusion to
clients.
Maybe it is better to start a discussion on dev@
> Add Client/Server API to return available features
> --------------------------------------------------
>
> Key: ZOOKEEPER-3762
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3762
> Project: ZooKeeper
> Issue Type: New Feature
> Components: c client, java client, server
> Affects Versions: 3.6.0
> Reporter: Jordan Zimmerman
> Priority: Major
>
> Recent versions have introduced several new features/changes. Clients would
> benefit from an API that reports the feature set that a server instance
> supports. Something like (in Java):
> {code}
> public enum ServerFeatures {
> TTL_NODES,
> PERSISTENT_WATCHERS,
> ... etc ... full set of features TBD
> }
> // in ZooKeeper.java
> public Collection<ServerFeatures> getServerFeatures() {
> ...
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
