<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Sep 30, 2014, at 10:12 PM, Joshua Bartlett <<a href="mailto:josh@bartletts.id.au">josh@bartletts.id.au</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On 1 October 2014 14:09, Glyph <span dir="ltr"><<a href="mailto:glyph@twistedmatrix.com" target="_blank">glyph@twistedmatrix.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="h5"><br></div></div><div>That said: why did you need a threadpool of daemon threads?</div></div></blockquote><div><br></div><div>That's a very good question. One of my comaintainers thinks the answer is, "My codebase is old enough to vote and to answer your question I'd probably have to turn our SVN server back on. Please don't make me." :-)</div><div><br></div><div>I think the real reason is that the third-party library that we're calling from the threads sometimes takes a really long time to return, which means that unless we use daemon threads the only timely way to shut down / restart the service is kill -9, which is not ideal.</div></div></div></div></blockquote><br></div><div>Aah. That's a very good reason, come to think of it. Maybe we should default to daemon threads at some point in the future, for that matter; it would make exiting easier, by allowing us to still join() all the threads, but still exit if attempting to do so times out.</div><div><br></div><div>-glyph</div><div><br></div></body></html>