[
https://issues.apache.org/jira/browse/ZOOKEEPER-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062108#comment-17062108
]
Jordan Zimmerman commented on ZOOKEEPER-3762:
---------------------------------------------
We have a lot of code in Curator that tries to detect what features are
available as we'd like to use the same client JAR for ZooKeeper 3.4, 3.5, 3.6.
This would make that less hackish. But, I can also understand that it might be
overkill.
> 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)
