Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: Thread question Date: Wed, 30 Nov 2011 06:10:41 -0800 Organization: Canadian Mind Products Lines: 23 Message-ID: References: <081cd7paqgsa8bbg5gjh8v1kinfp7asgt0@4ax.com> Reply-To: Roedy Green NNTP-Posting-Host: Z2l1DcCELS0rATq8NqV4Sw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10361 On Wed, 30 Nov 2011 02:32:14 -0800, Roedy Green wrote, quoted or indirectly quoted someone who said : >ThreadPoolExecutor is looking promising, though overly elaborate. I got my code to compile. Then I discovered something quite idiotic about the class, Quoting Goetz et al "There is no predefined saturation policy to make "execute" block when the work queue is full." Huh? is that not the most common case? So it looks like I have to compose a custom blocking policy handler. -- Roedy Green Canadian Mind Products http://mindprod.com For me, the appeal of computer programming is that even though I am quite a klutz, I can still produce something, in a sense perfect, because the computer gives me as many chances as I please to get it right.