Martin Desruisseaux wrote: >> I have also implemented: >> - ThreadPoolProcessExecutor - implementation of ProcessExecutor > I presume that it uses java.util.concurrent.ThreadPoolExecutor under > the hood? It is an extension of that class. > Just for my information: is there any chance to avoid this copying and > instead just wrap the standard FutureTask and delegate most methods to > the wrapped instance? None I am afraid; the FutureTask implementation is actually just a very careful wrapper around a FutureTask.Sync internal class protected using the usual java 5 concurrency tricks (that I wish they would document). So yeah there is some technical debt here; someone will need to implement a ProgressTask of our own.
Jody ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
