Github user anmolnar commented on the issue:
https://github.com/apache/zookeeper/pull/545
@hanm Trying to make the API consistent by keeping one setter and getter
for the property. It escalated a bunch of other changes which I think are good
improvements and made the code simpler: e.g. removed checks for
secure/non-secure ServerCnxnFactory, because now we only have one.
But. It introduced an API change (no separate setter for the secure case
and signature has been changed for the non-secure). This might be a problem for
dependent projects like Curator which already takes advantage of 3.5 version.
We could keep the original API and setting the `secure` field appropriate
to stay on the safe side, but that won't satisfy your suggestion.
---
