Gustavo Niemeyer wrote:
* Netty - allow encryption btw servers (potentially clients too)
Yes! Yes! Both server and client, please! As we discussed, we want to
use ZooKeeper as a coordination service within a network which
shouldn't be *entirely* trusted, and this is a critical feature for
I believe Ben's worked out most of the server-server comm changes, but
there are still many rough edges I planned to take up and work out. We'd
need ppl to test it. If it's something you'd want to use it would be in
your best interest to do so prior to the release. Client-Server support
is a different matter, we'd have to see how the server works out first
re release timing.
* split out client tests, allow running against mocks as well as various
versions of server
* improve C client testing
* test container support
* split out zab? (might be useful as a library for third parties)
What is zab?
zab is the atomic broadcast used by the servers to communicate changes.
Feel free to respond to this email with any thoughts, suggestions, etc...
Do you think there's any chance that the ephemeral parents that were
mentioned in another thread could see some attention within this
Depends if someone is interested enough to work on it. ;-) It's an
interesting project that's not too difficult however there hasn't been
much deep thinking on it yet to uncover all the potential difficulties.