Damian Janowski 5053b327f1 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.		2012-12-18 14:05:13 -03:00
..
connection_pool	Doc, bump version	2012-06-29 20:22:42 -07:00
connection_pool.rb	Restore Wrapper inheriting from BasicObject. Closes #16.	2012-12-18 13:50:12 -03:00
timed_queue.rb	Checking in pushes objects to the head of the queue.	2012-12-18 14:05:13 -03:00