torquebox/torquebox — comment on commit 82252a8cf28432c0cdfe7f98f31fb245d34d6fbf
File:  line 0
By bobmcwhirter:

So I've given it more thought, and I think we can replace the startAsync stuff inside the pool with PASSIVE and MSC's async. We have broken the pool into a CREATE and a START, and MSC gives us an async. So I think we can make web depend on the CREATE, have START occur passively when possible, and everything is fine, and nobody waits for the start. While removing the pool's start async thread from inside it.

The deferred bit, though, I think should stay in the pool, since it's purpose was to not waste any resources until someone actually needs it. Biggest case being a plain app that uses no messaging, and we didn't want backgroundable to create/consume a Ruby.

I'll give it more thought and discussion before merging, definitely.