The connection pool will automatically create another connection to the same server if there are no existing unused connections left. So without terminating the timed out requests they will stack up a number of connections, but not directly influence later requests. For termination, I'll first have to add some new function to provide access to the TcpConnection.close function in some way.

What do you mean by 'unused connections'? How do you support http pipelining?

So right now this means that the connection is idle: no requests or responses are pending.