I think so, but the unbound queue here is just to simulate the behaviour of poolboy, the error/overflow control is more fine grained than in poolboy, where checking out the worker is always a max timeout no matter if it’s overloaded or not, and always makes the call (and can only know if it’s overloaded after the call returns or timeouts). In this queuer you can bail out immediately on overload, only bail out after X, bail out after X OR overload, and/or have a 0 max waiting queue, an unbound queue or a finite queue.
[edit] - the timeout is not hardcoded in poolboy duh
