GitHub user eolivelli opened a pull request:
https://github.com/apache/zookeeper/pull/227
ZOOKEEPER-2755 Allow to subclass ClientCnxnSocketNetty and NettyServerCnxn
Little refactoring to use only SocketAddress instead of RemoteSocketAddress
and make it possible to create subclasses of ClientCnxnSocketNetty and
NettyServerCnxn which leverage built-in Netty 'local' channels.
Such Netty local channels do not create real sockets and so allow a simple
standalone ZooKeeper server + ZooKeeper client to be run on the same JVM
without binding to real TCP endpoints and run concurrent test processes of the
same application without dealing with random ports.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/eolivelli/zookeeper
ZOOKEEPER-2755-localaddress
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/227.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #227
----
commit fa306e830964b187f11aa5d08770feeaca72cd48
Author: eolivelli <[email protected]>
Date: 2017-04-13T04:55:43Z
ZOOKEEPER-2755 Allow to subclass ClientCnxnSocketNetty and NettyServerCnxn
in order to use Netty Local transport
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
