In case the NeoConfig enabled constructor is used, the TCP_NODELAY
can't be set downstream, because it needs to be set before the nodes
are added, and the swarm user is not able to do that if the nodes are
added in the constructor. This simply turns the TCP_NODELAY on when
constructing the neo client.
Adding it here to fix the issue in swarm v4.6.x/v5.0.x - this behaviour is on by default in the next,
not yet released minor.
In case the NeoConfig enabled constructor is used, the TCP_NODELAY can't be set downstream, because it needs to be set before the nodes are added, and the swarm user is not able to do that if the nodes are added in the constructor. This simply turns the TCP_NODELAY on when constructing the neo client.
Adding it here to fix the issue in swarm v4.6.x/v5.0.x - this behaviour is on by default in the next, not yet released minor.