The behaviour that motivated TINKERPOP-1774 was the unbounded number of connections that was being created, but it's true that references the java driver as the reference implementation, sorry about that.
I think having a fixed amount of connections leads to a predictable behaviour (latency / resource provisioning / etc) and a simpler implementation. With request pipelining, there are few cases where the user will need more than 1 connection (in that case, the user can configure a different fixed number). [ Full content available at: https://github.com/apache/tinkerpop/pull/1016 ] This message was relayed via gitbox.apache.org for [email protected]
