Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of oliver.zeigermann@gmail.com
 designates 64.233.182.189 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=ImoVInCS09JKYkL7tdLXUWQlGJd8VTRxm7VvS+huZM26hPVn5I1G4UMrWEzrMm6AtFWbMhT/1r8HN+x86NyY2vcuA/U+2V1fEd5++/ULLAT2YDhEM+ykwwHUvpIfmtOuRkeMGIb3E5yKsvij804NjwQAK/I8VOk+lvhgtNj7PLo=
Message-ID: <9da4f4520710031431g433b0e9are2eaae8a6dc70f03@mail.gmail.com>
Date: Wed, 3 Oct 2007 23:31:11 +0200
From: "Oliver Zeigermann" <oliver@zeigermann.de>
Sender: oliver.zeigermann@gmail.com
To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Subject: Re: POLL: Anyone interested in a new CONCURRENT component
In-Reply-To: <470407FE.4070802@sourcelabs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9da4f4520710031300p668262e5kb4b266a5807f9e25@mail.gmail.com>
	 <6185d22e0710031311w7b5b874dse1114ad093adfbde@mail.gmail.com>
	 <9da4f4520710031329jcc50bacy5b7ec4922021f0c4@mail.gmail.com>
	 <6185d22e0710031344g4e6e1f7dkf174ffca4c2acb71@mail.gmail.com>
	 <9da4f4520710031400g755cb122nfc1332879fcb0409@mail.gmail.com>
	 <470407FE.4070802@sourcelabs.com>

2007/10/3, Will Pugh <willpugh@sourcelabs.com>:
> Another idea (not well thought out) would be to try doing something like
> threadlets for Java (http://kerneltrap.org/node/7753)
>
> So that some operation would either execute directly, or if a lock is
> taken would spawn a thread to wait for access.  Not sure if it's a
> solution in search of a problem, since I haven't had need to use them
> yet, but I thought threadlets and syslets seemed like cool concepts on
> their own.

Not quite sure if this is possible without manipulating the JVM. Cool
idea, though...

> Another structure I've used a lot in UI programming is very similar to
> an ExecuterService, except that each task has executeBackground and
> exceuteForeground methods.  The executeBackground method is called on a
> pooled background thread.  The executeForground is then called on the
> main AWT thread.

This is a "SwingWorker" in the Swing world, right?

Oliver

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org