https://issues.apache.org/jira/browse/TINKERPOP-1774
https://issues.apache.org/jira/browse/TINKERPOP-1775

This allows connections to be reused for different requests in parallel which 
should lead to better utilization of connections / lower resource usage. The 
ConnectionPool now also has a min and max size. A new connection is only 
created if all existing connections reached their max in-flight limit (which is 
also a new setting). If additionally the max size of the ConnectionPool is 
reached, then an exception is thrown which makes this a breaking change.

This change fixes both issues together as discussed in PR #903.

All tests pass with `./docker/build.sh -t -i` and I verified that the changed 
docs look as expected with `./docker/build.sh -d`.

VOTE +1

[ Full content available at: https://github.com/apache/tinkerpop/pull/1016 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to