| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
It can be quite useful to allow the lock that the pool
uses to be specified to be something other than the default
threading lock class/type. This can be especially useful when
eventlet (or gevent or other) are used which have there own
special lock type that connects into there event-loop.
|
| |
|
|
|
|
|
| |
Avoid holding the pool lock while calling into
the 'after_remove' callback to ensure that no kind
of deadlock is likely to occur (say if the callback
calls back into the pool).
|
| | |
|
| | |
|
|
|
- Add a object pool that can create clients in a thread
safe manner (and release and destroy them as/when needed).
|
