Feature Request: Connection Pool Request Queue

[edward-coombes-nuodb]

When using the connection pool, when the hard limit is reached an error is generated. Another potential option for this would be implementing a connection request queue. When there are no connections to be distributed, the request would be added to a queue, and a promise for a connection returned. As connections are released back into the pool they would be given to requests in the queue in FIFO order.

[dwhite-nuodb]

Currently we only throw an exception when the hard limit is reached, or we allow the connection pool to expand on demand, so this feature would offer an alternative approach to handle over capacity demand. It is not scheduled for a release, but will get consideration for planning as demand for certain use cases dictate.