commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Pugh <>
Subject Re: POLL: Anyone interested in a new CONCURRENT component
Date Wed, 03 Oct 2007 21:56:31 GMT

Oliver Zeigermann wrote:
> 2007/10/3, Will Pugh <>:
>> Another idea (not well thought out) would be to try doing something like
>> threadlets for Java (
>> 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...
I haven't thought about it too deeply.  It's fairly likely that doing a 
compelling implementation would require VM support, but I'm sure there 
is some subset of functionality you could do . . .
>> 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?
Yeah it is.  I think SwingWorker is in the 1.6 JDK (but haven't been 
doing much UI work lately)
> Oliver
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message