Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/903
> I think implementing TINKERPOP-1774 with the current implementation of
the pool (dequeuing) comes at a cost of introducing complexity (in particular
AsyncAutoResetEvent).
I guess that depends on whether we want to implement TINKERPOP-1775 with
our without a `max in-flight` requests per connection as that would result in
some connections having to wait and therefore an `AsyncAutoResetEvent` would be
helpful again.
Without such a limit, I wonder when we would create new connections at all.
When we just round-robin incoming requests to connections in the pool, then
when should a new connection be created?
---