mperham/connection_pool — pull request #26 by djanowski (2012-12-18 17:10:27+00:00)
Title: Checking in pushes objects to the head of the queue.

This means that, when not saturated, objects in the pool will be reused
more often.

This behavior allows you to create a pool of objects which in turn have
some kind of time outs themselves. For instance, objects which keep an
underlying TCP connection open until they're idle for some time. An
example of this is `Net::HTTP::Persistent`.

See also issue #20.

@mperham Do you see any problems with this change?