aslakhellesoy/webbit — comment on commit 15f89e85f1f27619f342f2d1099f4c9f77c17dc8
File:  line 0
By osi:

yes, I have a shutdown hook that tries to orderly stop everything that was started.

I'm fine with the API breakage. was just wonder out loud if it was useful at all. if you think you'll you it, good enough for me :)

--
peter royal - (on the go)

On Feb 5, 2012, at 5:57 PM, Aslak Hellesøy wrote:

> I suppose using stop in production (I assume you're using shutdown hooks?) is the polite thing to do.
>
> The use case for async start/stop is the ability to wait for complete start/stop in a different thread than the one kicking it off. This might be a little speculative, but it "feels" right to me. It's possible to do other things while the server is starting/stopping so I guess a very minor speed gain is the use case.
>
> Any thoughts on what the proposed change might break?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/aslakhellesoy/webbit/commit/15f89e85f1f27619f342f2d1099f4c9f77c17dc8#commitcomment-934954